The main agenda of below document is to understood about number ranges and Assignment to different Objects. In Implementation, finding decision on number ranges is crucial role. Once defined and created the documents or master data , it is very difficult to get back and change the number ranges for existing data. Before going to develop the blue print client have to take decision on Number ranges for different objects.

Number Ranges:

Every document or master data will be created with one unique number. This unique number will get from Number series , which was assigned to object. Number ranges need to define in each server. It's not transportable from one server to another server. Assignment group and code will be transportable but number series defining have to do in each server.

1) Define Number ranges and Material Type assignment :

There was little bit differences in present upgraded SAP servers and old SAP server in screens for defining the number ranges and assignments for material types. But procedure was same.

• Ø You can’t define directly number ranges to material types, you have to create group and assign material type to this Group.
• Ø Multiple Material types can be assign to one Group.

1. Path: SPROà F5 à Logistic General à Material Master à Basic Settings à Material types à Define Number ranges for each Material type

OR

You can directly enter T-code: MMNR

In Old version ----

Click on Groups(change)

Go to Group---> insert

In new version ----

Click on groups(change)

click on create buttion.

OR

You can go with SNRO, enter Object name as mentioned below.

Object Name: MATERIALNR (Material Master Number Ranges).

Click on Ranges after entering the Object

Create Group and assign material type to group.

2)Define Number ranges and Vendor Account Group assignment :

1. Path: SPROà F5 à Logistic General à Business Partner àVendorsà Control à Define number ranges for vendor master records

Or

You can directly enter T-code: OMSJ

Or

You can go with SNRO, Enter object name as mentioned below.

Object Name: KREDITOR (Vendor Number Ranges).

3) Define Number ranges and Purchasing Info record Document type assignment :

Path: SPROà F5 à Material Management à Purchasing àPurchasing info record  à Define number ranges

Or

You can directly enter T-code: OMEO

Or

You can go with SNRO, Enter object name as mentioned below.

Object Name: INFOSATZ (Number ranges for Purchasing Info record).

Document type IL– Purchasing Info record for stock material.

Document type IN– Purchasing info record for material group (non-stock materials).

4) Define Number ranges and Quota Arrangement Document type assignment :

Path: SPROà F5 à Material Management à Purchasing àQuota Arrangement  à Define number ranges

Or

You can directly enter T-code: OMEP

Or

You can go with SNRO, Enter object name as mentioned below.

Object Name: QUOTIERUNG (Number ranges for Purchasing Info record).

5) Define Number ranges and  RFQ/Quotation Document type assignment :

Path: SPROà F5 à Material Management à Purchasing àRFQ/Quotation  à Define number ranges

Or

You can directly enter T-code: OMH6

Or

You can go with SNRO, Enter object name as mentioned below.

Object Name: EINKBELEG (Number ranges for Purchasing Documents).

Here you can define Number range Code like 01, 02, 03…XX.

And need to assign these codes into your document types – Mentioned path below

Path: SPROà F5 à Material Management à Purchasing àRFQ/Quotation  à Define Document type.

6)MDefine Number ranges and  Purchase Requisition Document type assignment :

1. Path: SPROà F5 à Material Management à Purchasing àPurchase Requisitions à Define number ranges

Or

You can directly enter T-code: OMH7

Or

You can go with SNRO, Enter object name as mentioned below.

Object Name: BANF (Number ranges for Purchasing Requisition).

Here you can define Number range Code like 01, 02, 03…XX.

And need to assign these codes into your document types – Mentioned path below

Path: SPROà F5 à Material Management à Purchasing à Purchase Requisitions   à Define Document type.

7) Define Number ranges and  Purchase Order Document type assignment :

1. Path: SPROà F5 à Material Management à Purchasing àPurchase Order à Define number ranges

Or

You can directly enter T-code: OMH6

Or

You can go with SNRO, Enter object name as mentioned below.

Object Name: EINKBELEG (Number ranges for Purchasing Documents).

Here you can define Number range Code like 01, 02, 03…XX.

And need to assign these codes into your document types – Mentioned path below

1. Path: SPROà F5 à Material Management à Purchasing à Purchase Orders   à Define Document type.

8) Define Number ranges and  Purchase Order Document type assignment :

Path: SPROà F5 à Material Management à Purchasing àPurchase Order à Define number ranges

Or

You can directly enter T-code: OMH6

Or

You can go with SNRO, Enter object name as mentioned below.

Object Name: EINKBELEG (Number ranges for Purchasing Documents).

Here you can define Number range Code like 01, 02, 03…XX.

And need to assign these codes into your document types – Mentioned path below

Path: SPROà F5 à Material Management à Purchasing à Purchase Orders   à Define Document type.

9) Define Number ranges and  Contract Document type assignment :

1. Path: SPROà F5 à Material Management à Purchasing àContracts à Define number ranges

Or

You can directly enter T-code: OMH6

Or

You can go with SNRO, Enter object name as mentioned below.

Object Name: EINKBELEG (Number ranges for Purchasing Documents).

Here you can define Number range Code like 01, 02, 03…XX.

And need to assign these codes into your document types – Mentioned path below

1. Path: SPROà F5 à Material Management à Purchasing à Contracts   à Define Document type.

Document type MK – Quantity contract

Document type WK – Value contract

10) Define Number ranges and  Scheduling agreement Document type assignment :

Path: SPROà F5 à Material Management à Purchasing àContracts à Define number ranges

Or

You can directly enter T-code: OMH6

Or

You can go with SNRO, Enter object name as mentioned below.

Object Name: EINKBELEG (Number ranges for Purchasing Documents).

Here you can define Number range Code like 01, 02, 03…XX.

And need to assign these codes into your document types – Mentioned path below

1. Path: SPROà F5 à Material Management à Purchasing à Scheduling agreement   à Define Document type.

Document type LP - Scheduling Agreement (without release)

Document type LPA – Scheduling agreement (with release)

Document type LU – stock transport Scheduling agreement.

11) Define Number ranges and  Service entry sheet  Document type assignment :

Path: SPROà F5 à Material Management à External service management àNumber range s à Define number                ranges for service entry sheet.

Or

You can directly enter T-code: OMH9

Or

You can go with SNRO, Enter object name as mentioned below.

Object Name: SERVICE3 (Number ranges for Service entry sheet).

Here you can define Number range Code like 01, 02, 03…XX.

Path: SPROà F5 à Material Management à External service management à Number ranges-à Assign number   ranges.

12) Define Number ranges and  Service Specification assignment :

1. Path: SPROà F5 à Material Management à External service management àNumber range s à Define Internal number ranges for service Specification.

Or

You can directly enter T-code: OMH8

Or

You can go with SNRO, Enter object name as mentioned below.

Object Name: SERVICE (Number ranges for Service Specification).

Here you can define Number range Code like 01, 02, 03…XX.

1. Path: SPROà F5 à Material Management à External service management à Number ranges-à Assign number   ranges.

13) Define Number ranges and  Service master  assignment :

1. Path: SPROà F5 à Material Management à External service management àNumber range s à Define Internal number ranges for service Specification.

Or

You can directly enter T-code: ACNR

Or

You can go with SNRO, Enter object name as mentioned below.

Object Name: LEISTUNG (Number ranges for Service master or cross application service master).

Need to define group with number ranges and assign to Service category.

Service Category:

1) GRND – Admin services

2) ALL- Other services

3) SERV – Service: Purchasing

14) Define Number ranges and  Accounting document Doc type assignment :

1. Path: SPROà F5 à Material Management à Inventory Management and Physical inventory àNumber assignment à Define number assignment for Accounting Documents.

Or

You can directly enter T-code: OMBA

Or

You can go with SNRO, Enter object name as mentioned below.

Object Name: RF_BELEG (Number ranges for accounting documents).

Here you can define Number range Code like 01, 02, 03…XX. At company code level and need to assign for your document type (for accounting document)

AA          Asset Posting

AB          Accounting Document

AF           Depreciation Postings

AN          Net Asset Posting

AS           Asset Sales

PR           Price Change

RA          Sub.Cred.Memo Settlement

RB           Reserve for Bad Debt

RE           Invoice - Gross

RN          Invoice - Net

RV          Billing Doc.Transfer

SA           G/L Account Document

SB           G/L Account Posting

SK           Cash Document

SU          Adjustment Document

PR           Price Change

RA          Sub.Cred.Memo Settlement

RB           Reserve for Bad Debt

RE           Invoice - Gross

RN          Invoice - Net

RV          Billing Doc.Transfer

SA           G/L Account Document

SB           G/L Account Posting

SK           Cash Document

SU          Adjustment Document

15) Define Number ranges and  Material document and physical inventory Doc type assignment :

Path: SPROà F5 à Material Management à Inventory Management and Physical inventory àNumber assignment à Define number assignment for material and Physical Inventory Documents.

Or

You can directly enter T-code: OMBT

Or

You can go with SNRO, Enter object name as mentioned below.

Object Name: MATBELEG (Number ranges for Material documents).

You have to create groups and assign document type to group.

Inventory documents:

IB Physical inventory documents
- ID Physical inventory documents for counts and differences
without reference
- IN Physical inventory documents for recounts
- IZ Physical inventory documents for count without reference
- WV Physical inventory documents for difference postings in the WM System

Material documents for goods movements and inventory differences

  - WA Goods issues, transfer postings, other goods receipts

- WH Goods movements for handling units (HU)
- WI Material documents for inventory adjustment postings
- WL Goods issues for delivery documents (SD)
- WQ Goods movements for usage decisions (QM)
- WR Goods movements for completion confirmations (PP)
- WS Goods movements for run schedule headers (PP)

- WZ Documents for batch status changes

Material documents for Goods Receipts:

- WE Goods receipts for purchase orders
- WF Goods receipts for production orders
- WO Subsequent adjustment of subcontract orders
- WW Subsequent adjustment of active ingredient materials

Inventory sampling numbers

-SI

16) Define Number ranges and  Reservation  Doc type assignment :

Path: SPROà F5 à Material Management à Inventory Management and Physical inventory àNumber assignment à Define number assignment for material and Physical Inventory Documents.

Or

You can directly enter T-code: OMC2

Or

You can go with SNRO, Enter object name as mentioned below.

Object Name: RESB (Number ranges for Reservation).

You have to create code with number range and assign in No. range reservation/dependent requirement.

17) Define Number ranges and  Incoming invoice Doc type assignment :

Path: SPROà F5 à Material Management à Logistic Invoice verification à Incoming invoiceà Number assignment à Maintain Number assignment for logistic documents à Maintain Number range Intervals for invoice documents

Or

You can directly enter T-code: OMRJ

Or

You can go with SNRO, Enter object name as mentioned below.

Object Name: RE_BELEG (Number ranges for Invoice verification).

You have to create code with number range and assign No. range code to transactions in below patch

1. Path: SPROà F5 à Material Management à Logistic Invoice verification à Incoming invoiceà Number assignment à Maintain Number assignment for logistic documents à Transaction –Assign number range

• RD Post invoice
• RS Cancel/reverse invoice, ERS, EDI invoice receipt, invoicing plan, and revaluation.

OSS Note for Number Ranges:

1. Oss Note : 1785208

Various errors occur during material master number range creation (transaction MMNR)

1. Oss Note : 1793671

SNUM: Assignment of element to group not possible

1. Oss Note : 1778386

SNUM: Groups are not transported

1. Oss Note : 1774625

SNUM: Creating an external interval

1. Oss Note : 1765341

SNUM: Group Creation

1. 6)      Oss Note : 1746507

SNUM: Elements and groups

1. 7)      Oss Note : 1742191

SNUM: Saving Intervals

1. 8)    Oss Note : 504875

Buffering Number ranges

1. 9)    Oss Note : 678501

System stoppage, locks on table NRIV

1. 10) Oss Note : 572905

NR: UN-Buffered number ranges

1. 11) Oss Note : 62077

Info: Internal number assignment is not continuous

1. 12) Oss Note : 333356

Internal order: order numbers not assigned continuously

1. 13) Oss note : 16236

Create material: error in ext. Number assignment

1. 14) Oss Note : 72286

Lexicographical <-> non-lexicographical material no.

1. 15) Oss note : 78093

Display of alternative material identifiers

Hope this document will be help full to all in Implementation and in fiscal year activities.

KANBAN Process for External Procurement

What is KANBAN:

Kanban is a Japanese word with the meaning Signboard or Billboard and basically a card contain the details like the required material and its quantity and where the material is required. Normally during the production, if there exists a system of scheduling which takes care of immediate requirements of the Production  for the delivery as and when required say Just In Time rather when needed , would reduce the Lead Times and Inventory and provides a continuous flow for Production which does not stop the  lines of Production..

The process with this name KANBAN has been designed to take care of such requirements which will schedule the logistics chain as and when required for the Production Line. In this process the requirement for replenishment will be triggered by Production. This triggering will be in the form of a Signal (KANBAN SIGNAL ) in the place of kanban card manually which will consists of Required material and Quantity and the work area where it is required and will be sent directly to the work area ( Source vendor / Production area where its manufactured ) . Soon after the material is received the Goods Receipt can be posted automatically through the signal at the source of Demand.

KANBAN a Simplified Version:

Worthy points for KANBAN

The components which have to be consumed should be constant for a period of time which should be the longer than the replenishment lead time of the component.

The supply source should be capable of producing large quantities in small lots with in a period.

Few key words to be noted worthy.

Control Cycle: A control Cycle defines the relationship ouibetween the demand source such as a production line and the supply source such as an External Source.

Work area: Is an area at which the demand for the material exists and at which this material is utilized for the production of another component

JIT CALL: Is a Just In time call is a signal which will be generated in the system and which will contain the details like the material, required quantity, Delivery date, and the material Required Plant and the supply area which will receive the material and supply to the demand area of production, to whom the details to be send which is the vendor based upon the scheduling agreement.

Scheduling Agreement: Scheduling Agreement is an Agreement with the vendor for a supply of the required material for a JIT CALL quantity with the schedule of delivery.

Kanban Quantity: It is the quantity allotted for a KANBAN upon which needed to get filled with when emptied.

KANBAN Procedures:

There exist different procedures available for KANBAN based upon the control of Production and Operational structures.

Classic KANBAN: This procedure will be used to replenish the material for the number of Kanbans that circulates between the supply source and the demand source and the quantity per kanban.In this type of kanban the number of kanbans are fixed as per the control cycle and the quantity in the control cycle and also the signal will get triggered for the quantity per kanban defined in the control cycle.

Event Driven KANBAN: In the Event Driven kanban, the material is not made available continuously at a production supply area, but is procured when the material is requested. This does not depend upon the number of kanbans in the control cycle or the quantity in the kanban of the control cycle.

One Card KANBAN: With this approach, replenishment is always triggered when the kanban from which material is currently being withdrawn is approximately half empty. The new kanban then arrives before the current kanban has been completely emptied. This is very much useful when the material is not needed from time to time.

KANBAN with Quantity Signal: In the Classic KANBAN, the signal will be made to Empty when the operator makes it to empty when the KANBAN quantity reaches to ZERO and will not be knowing the current level of quantity prior becoming to zero. In contrast to Classic variety , in this model the operates c n enter the quantity and system can make the signal to Empty when emptied automatically as soon the kanban quantity is reached .

With the above basic introduction on the kanban and its processes, the below paragraphs will describe how a KANBAN can be dealt for external procurement.

               KANBAN CLASSIC PROCESS FOR EXTERNAL PROCUREMENT:

Step 1: Maintain Supply Area

Transaction Code: PK05

Upon Enter and with new entries:

Step 2: Create Control Cycle:

Transaction Code: PKMC

Upon you press enter along with the material entries with the plant and supply area; system will lead to a screen where in you need to maintain the number of kanbans, kanban quantity and the external procurement details.

In the External Procurement field we need to select one JIT CALL required  and soon after selecting the prifile , system will ask for a Schedule Line Aggrement with the item number of the material .

In the Flow Control Field provide the JIT CALL Profile and provide a print control detail in the tab.

Pre Requisites for Control Cycle:

1. Schedule Agreement at ME31L with a Schedule line
2. Message Output design at NACE for the JIT CALL signal Print /mail /fax etc.
3. Configuration for JIT CALL profile, JITCALL calculation profile details etc.

STEP 3: Kanban Signal Generation

Transaction code: PK21 (Manual Entry): In the KANBAN control process, signal generation place an important role. Though there exists many ways of doing the same, this write up concentrates on the Manual signal generation.

In the above screen provide the control cycle number and kanban number earlier created and press enter. System will populate the control cycle details.

Upon Press save system move the status from WAIT to EMPTY to generate a JITCALL to the vendor.

With proper settings for the output and a condition record for the output type system will send a mail or a Print to send to vendor or Fax etc.

STEP 4:  Out Put the JIT CALL

Transaction code: PJNA

The Jit call generated in the above step will be send to the vendor using the transaction code PJNA with the Output type entry and upon execute, system will lead to the send screen.

Based upon the Transmission mode and its form and configuration settings at NACE, we can either FAX/EMAIL/PRINT the JIT CALL.

Step 5: Making the Goods Receipt upon the Receipt of the Material:

Transaction Code: PJWE

Through this transaction we can automatically receipt the received materials into the supply area.

And upon enter the screen system will lead to

And upon provision of the received quantity and saving the screen system will post the GR.

Conclusion:

This is how the external procurement for KANBAN will work for the Classic KANBAN

Order fulfillment for ship complete scenario

Overview:

There are many ways of order fulfillment and most of them are based on how the material is classified ie Make to stock, Make to order etc.

1. Make to Stock Order fulfillment
Here the stock is readily available based on the forecast and mostly stored in Centralized warehouse for quick response to customers demand.

2. Make to Order or Configure to order fulfillment

In make to order scenarios the product ordered by the customer is a customized one and hence is build only when the order is inducted in the system

These orders are not fulfilled from warehouse rather those order go to plant where these products are build as per customers requirement and then shipped out

3. There are certain scenarios where customer demand both Make to order and Make to Stock product in a single order and they want to have both the products delivered in single shipment

So here for the make to stock line item the plant defaulted is warehouse plant (MAR1), where as for the make to stock line item the plant defaulted is plant (MAR2) .So in order to ship both the products should have same delivering plant.

Thus below we have discussed one of the method to achieve the same and configuration setup required from SD, MM & APO end

Summary of outcome from the changes done

• In this scenario as soon as the complete delivery tab in SO is selected the plant for make to order based line item will be changed from MAR2 to warehouse plant MAR1 based on the multi item single location config maintained in APO
• Post this the schedule line of the order based line item will have a purchase requisition which when converted to PO is an STO to transfer the stock from MAR2 to MAR1 once the same has been build in MAR2 plant as per customers requirement.
• Once both the stock is available in warehouse plant MAR1 the DN is dropped and order is fulfilled

1. SD related Configuration Steps:

• Configure schedule line category to create STO PR in schedule lines

1.1Creating Schedule line catergory “MA”

1. Sales & Distribution-->Sales-->Sales Document-->Schedule Lines-->Define Schedule line Catergories

Key Changes:

• Item category used as ‘7’ ie Stock Tranfer

  Account Assgnt Cat as ‘M’ ie Individual Customer w/o KD-CO

1.2 Assign the Schedule line category to the respective Item cat

2. APO related Configuration steps:

(To default the warehouse plant on setting the Ship completed tab)

We can use APO Rule based ATP functionality to make “Complete delivery” Sales order to point to a single plant. For this we need to use the rule type MISL (Multi Item Single Location).

Rule based ATP check is an iterative, step-by-step availability check process driven by self defined rules. The results of one step determine whether the next condition type needs to be further processed and checked.

Configuration:

2.1 The Rule Based ATP check is enabled in the Check Instruction.

The Check instruction is the combination of Check mode and business Event.

So the Check instruction for this part must have the Rule based indicator set up so that Rules are called as required.

At this point assumption is that the Condition table, Access sequence, Strategy sequence is already setup.

2.2 The MISL rule also activated in SPRO >> Advanced planning and optimization >> Global Available to promise >> Rule based Availability check >> Activate Multi – Item single delivery location.

2.3 So the Rule type to be used is defined in the APO >> Mater data >> Rule Maintenance >> Integrated Rule maintenance

Further the condition type has to be specified showing when order is marked as “Ship complete” then it should call MISL rule.

3. MM related configuration steps and Master Data Setup

3.1 Master Data Setup:

• Auto PR to PO conversion
• STO Pur-Req should have the source of supply defaulted, the same will be fetched from Source list

  Tcode:ME01

Note: PPL ie Procurement plant maintianed is MAR2

• Autom.PO field set in Material-Master

• Material Requirement PLanning

MRP run on plant MAR2 will create purchase requsition

• Pur-Req will have source of supply defaulted from below source list

Note:

• Vendor 233 is used for external procurement
• MRP field is set as ”1” for MRP run

End to End Cycle of above process:

Sales Order:

Select line item 20 & click on “Item Details Configuration”

STO PR:10018013

Once the STO PO is created check the Stock requirement list of the delivering plant i.e MAR1, there will be entry for SO & the corresponding STO PO

MRP RUN on Plant MAR2

Tcode:MD02

Pur-Req created.

Stock/Requirement list for Plant MAR2

Pur-Req:10018105

PR to PO conversion:
Procurement PO :1002020006

• GR against the ZCON PO:

Stock is received in Plant MAR2, Sloc MAS3 and is mapped to the SO:16089

Stock to be transferred from plant MAR2 to warehouse MAR1
Outbound Delivery against STO 4500019858
Tcode:VL10B

Movement Type : 641
The quantity is transferred unrestricted-use stock of the issuing plant to 'stock in transit' of the receiving plant.

Author:

Sivakumar Arumugham : SAP-APO

Maruti Shingade : SAP MM-Logistics

Hi Guys,

I would like to share Comments on how client has given important preference for Performance on execution of transaction, Developments and Report.

What we can find through analysis from sap. How to get performance results in SAP for each execution and Back ground Jobs.

Transaction code for business transaction analysis is STAD.

enter

Go to Menu bar Monitor --> performance---> Response time

Here you can get detailed analysis of Business transaction analysis

What we can find from business transaction analysis?

1. Can easily find performance for each transaction on overall users or particular users.
2. Can easily find performance for each Program.
3. Can easily find performance for each back ground job for each user or overall.
4. Can easily find from which server and Transaction and Program and user.
5. Can easily find Response time and memory used in terms KB for each transaction and Program and user.
6. Can easily find day by day how much memory using based on task types                    
7. Can easily analyse how many calls per day based on task type or program.     
8. Can easily find Work load overview

Through Transaction code: ST03N also we can analyse the performance for transaction.        

ST03N  is transaction to direcly check work load monitor analysis.                         

Generally we have to analyse three external activities which will get more performance issues           

1. Transaction codes
2. Reports
3. Developments/ coding impact on running transaction and Reports.
4. Having performance issues with Transaction execution and posting the Documents?         

Performance issue will get generally, because of huge records in Table level.

For example running MIRO transaction performance very slowly while posting and while checking the data. -    Why the performance issue rising in particular transaction and How to resolve it?                                                                                                                                                                                                                                                             

Solution: In standard tables there was lot of huge records and while running transaction, program calling dependent tables, which have more data. To avoid this we have to create secondary index in Table level by using ABAPer.

In SAP we have two indexes 1) Primary index and 2) secondary index.

1. Using primary keys will create automatically primary indexes. Used for primary keys in table.
2. Secondary should be create manually as per the user requirement.

Secondary index is help full to effective way of retrieving the data from data base tables.   

Index is like helping to you get easily data for your query.

It is not only use for Transactions, for reports also we will be create index. To generate the customized report with fast performance, Abaper will create indexes on dependent tables.

http://www.****************/Tutorials/ABAP/SecondaryIndex/Create.htm

Please refer above link explained how to create secondary index in Transparent table.

**************** - Creating a secondary index

389359 - MIRO: Performance problems check double invoice

Please refer above note and link explained how to create secondary index in standard table

1. Having performance issues with Report execution and generating output?          

Sometimes based on selection screen - system will perform and will take to execute the report.

Please refer below link

http://scn.sap.com/community/erp/logistics-mm/blog/2013/06/27/having-performance-issues-with-reporting-in-purchasing-with-me2-transactions

Arminda Jack explained clearly based on selection criteria the report performance get quickly. Thank you.

Please refer below link is explained standard report MB51 Performance improvement.

http://www.sapfix.com/tag/mb51-performance-problem/

1. Having performance issues with running of batch run for reports to get output? 

When we get query on this, first we have to look into whether this batch run related to standard report or customized report. Mostly reason for customized report is coding.

We have to look into mostly into coding part which have more loops and FM and call functions which will be impact on performance of report.

Please refer below link explained reduce run time of batch program

http://scn.sap.com/community/abap/testing-and-troubleshooting/blog/2013/04/26/how-to-reduce-run-time-of-program

Below Mentioned SAP notes on Performance

SAP Note 352979 - Collective note: Performance notes for IS-AFS-MM

SAP Note 134660 - Logistics Invoice Verification: Performance (RBKP)

SAP Note 158519 - Performance optimization in logistics invoice verification

SAP Note 311089 - Performance problems because of long PO history

SAP Note 389359 - MIRO: Performance problems check double invoice

SAP Note 756292 - Consulting: Performance MIRO Enter invoice

SAP Note 1143682 - MIRO/MIR7: Performance when entering an invoice document

SAP Note 191492- Performance: Customer developments in MM/WM

SAP Note 921164 -    MB51: Improving the runtime using database hints

SAP Note 902675-     MB51: Database hints to improve runtime / 4.70

SAP Note 1283280-     MB51: Enhancements to multiple account assignment display

SAP Note 1233616-     MB51: Bad performance by selection material numbers

SAP Note 555893-     MB51: Preventing runtime error DBIF_RSQL_INVALID_RSQL

SAP Note 1159120-     MB51: Selection of material numbers not quite correctly

SAP Note 531604-     MB52: Performance improvement

SAP Note 540257-     MB52: Performance improvement (only for Release 4.5B)

SAP Note 129599-     MB52: Performance, incorrect display

SAP Note 1516684 MKPF fields added to MSEG – Performance optimization

SAP Note 1550000 MB51: Redesign of selection for performance optimization

SAP Note 1558298 MB5B: Redesign of selection to optimize performance

SAP Note 1567602 DB dependent steps to support the redesign of MB51

SAP Note 1598760 FAQ: MSEG Enhancement & Redesign MB51/MB5B

Hints: In SAP MM mostly will get performance issues in MIGO and MIRO. Why because there was huge records in standard tables like MSEG, EKBE, RBKP, and BSIP…

My humble request was if you are getting performance issue in MIRO, Please check first whether secondary index create in MSEG table or not.

Create secondary INDEX for MSEG table with the following fields as mentioned in note 413446 also.
Table MSEG: (Additional Index for CIN)
- Index: Index for reference documents.
MANDT
LFBJA
LFBNR
LFPOS

If doesn't work you can check if you are using the duplicate invoice.
Putting an index on RBKP (see note 134660) and BSIP (see note 389359)
could greatly improve the MIRO performance.

If in case if you have still issues then ……

In order to analyse, we need to create SQL trace from transaction ST05 for the user that will use transaction MIRO. First hit ST05 and hit Trace on. Then go to MIRO (and complete the transaction).Go back to ST05 > SWITCH OFF Trace. Hit Trace List > Here you should be getting the trace results. Please provide result to SAP, the analyse of this. They would like to ask you to check which tables are involved (most time) in the process?

Normally the creation of secondary indexes for MSEG
should suffice for considerable performance improvement as this avoids
a full table scan of MSEG

For reference please look into below link

http://scn.sap.com/people/carla.bussolo/blog/2015/01/28/focus-is-on-miro-performance

Carla Bussolo explained very well on MIRO performance. Thank you..

Hi,

This is common requirement getting from client. I want to share this to all. I hope for freshers and users it is helpful;

Requirement : GR value and qty , IR value and qty and balances can be viewed on purchasing organization basis using the T Code: MB5S. User requirement is need results for this report automatically through mail to HOD every day.

Means every day for this report results need to send automatically mail with out executing manually.

The below are steps for achieving this requirement.

Step 1: create Distribution lists in SO23

Click on create button.

Enter name and title

click on f4 functionality in place of folder.

click on create folder

enter folder and name and click on enter

click on enter

click on Distr.list content tab

enter your mail id in place of recipient and Recip. type

Here three boxes is there , purpose of these is

1) Send Express :

If you select this field, this document is sent to the recipient as an express message. A dialog box then appears informing the user that an express document has been sent, allowing him/her to switch to the inbox.

2) Send Copy :

If you select this field, the user receives the document as a copy. This means the user receives the document for his/her information and does not need to take any action.

3) Send : blind copy :

If this field is selected, the recipient receives the document as a blind copy.

Save.

Step 2:  Execute Report with your requirement

T-code : MB5S

enter data in selection screen

Save as variant.

save

go to menu --> Program--->execute in back ground

click on date/time

select schedule start

and click on Period Values

Here you can select period values like hourly ,daily, weekly, monthly , other period means you can select job start  like every minitiues

Here i selected every 5 minutes i need  report results .

click on save.

Go to T- code SM37 :

enter Job name : * and execute

After five minutes you refresh the screen

It shows activity finished and it will show spool in the field of spool.

go to menu ---> JOB ---->chnage

click on spool list recipient

click on detail search

and enter and click on copy

click on F4 on recipient

and click on f5

save

You will get mail after five minutes with results of report.

Hope its helpful to all.

Dear Friends,

I would like to share with you a scenario, which I've come across in 'PO Release Strategy' and solved by doing a small enhancement, as there was no solution in 'Standard SAP' (confirmed by SAP).

The Scenario:

Example: PO Release Strategy is configured for 3 level as explained below;

1st Level:      L2 - Local Purchase Manager

2nd Level:     L3 -  Finance Manager

3rd Level:      GM - General Manager (Highest Level)

In standard SAP for the current scenario, SAP has provided a provision to 'Local Purchase Manager' (1st Level) / Finance Manager (2nd Level) to revoke the purchase order, which is released completely by 'General Manager' (3rd Level). Few business advise to restrict this functionality, as they expects the functionality like, once the PO gets released by General Manager, neither Finance Manager nor Local Purchase Manager should have the authorization to revoke the PO, until the General Manager revokes it.

Solution:

Restricted the release authorization at the role level for the transaction code ME29N, by doing screen enhancement. Since the requirement is not achievable in standard sap (confirmed by SAP).

Steps:

1. Go to transaction code ME29N--> enter purchase order number, which is waiting for release--> enter /h (debug mode) in command bar--> then click on ‘Release Strategy’ tab in PO header-->it would take you to the program ‘SAPLMERELVI--> find out for the ‘Include - lmerelvici1-->double click on the include and then go to method ‘HOTSPOT_CLICK--> write the restriction logic for the desired roles as shown in below logic.

Transaction Code: ME29N

Program Name: SAPLMERELVI

Include Program: LMERELVICI1 

In Method: HOTSPOT_CLICK

Fucnctional Logic:

1. Once we go to the transaction ME29N to release the PO, the program would check for the PO release status (Structure: MEPO_REL_GENERAL- FRGKX≠ R or (Just for reference: EKKO-FRGRL=X))--> if the PO is not completely released (FRGKX ≠ R) skip the process-->  if the PO is released completely (FRGKX = R or (Ref: EKKO-FRGRL= ‘ ’)) go to table AGR_USERS (list of users) and check for the role--> if the user has role: 'GM:GENERAL_MANAGER', allow the user to revoke the PO--> if he doesn't has the given role, display an error message as 'You are not Authorized to revoke the Release Strategy, until final level revokes the PO'

ABAP Code:

IF sy-tcode = 'ME29N'.
TYPES: BEGIN OF ty_agr_users,
agr_name TYPE agr_users-agr_name,
uname TYPE agr_users-uname,
END OF ty_agr_users.

DATA : lv_user TYPE sy-uname,
it_agr TYPE TABLE OF ty_agr_users,
wa_agr TYPE ty_agr_users.

if MEPO_REL_GENERAL-FRGKX = 'R'.

lv_user = sy-uname.
SELECT
agr_name
uname
FROM agr_users
INTO TABLE it_agr
WHERE uname = lv_user.

READ TABLE it_agr INTO wa_agr WITH KEY agr_name = 'GM:GENERAL_MANAGER'.
IF sy-subrc <> 0.
MESSAGE 'You are not Authorized to revoke the Release Strategy, until the final level revokes the PO' TYPE 'I' .
EXIT.
ENDIF.
ENDIF.
clear : lv_user,it_agr,wa_agr.
ENDIF.

Result:

Local Purchase Manager is trying to revoke a purchase order, which has already released by Finance Manager & General Manager, but system is throwing an error message, as expected.

Hope this document is clear for you and helps you in your current or future project(s) .

Thank you for reading the document .

Narayana N

Hello Community ,

Background

When we have requirement to upload BOM to SAP with use of multi structures like sub-items or long text or requirement to provide simple interface tool to the end user to upload BOM data from excel to SAP, the following approach can be alternative to LSMW .
This BOM flat file spreadsheetgenerates flat files that can be uploaded to Standard Batch Input program for creating BOM ,This can save development of designated ABAP programs which writes data to a sequential file in the format required by the ABAP programs (RCSBI010 ,RCSBI040)

How to do it 

Step 1 : Create  template using structures (BGR00,BICSK,BICSP..)  - choose just the relevant fields .

Step 2 : Fill the BOM header and items data in the excel template create at step 1.

Step 3 : Press on Execute on the Excel ribon to generate Flat file

Step 4 : Upload the flat file generated at step 3 to the application server with transaction CG3Z

Step 5 : Run Transaction OS41.

See attached video tutorial link for step by step exemple for transaction CS01

Structurs information (From SAP help - program RCSBI010)

Record type 0: one session record (structure BGR00) per session

The session header contains general administrative data on the batch input session to be created.

All records that follow the header in the sequential file are assigned to the current session, until the next header occurs in the file.

Record type 1: one session record (structure BICSK) for each BOM The BOM header record contains the transaction code (for example, CS01

Create material BOM) and the header data. In the field BICSK-TCODE in structure BISCK, you define the BOM category. The BOM category determines the SAP transaction to be called.

The following entries are possible:

- CV11 for document structures

- IB01 for equipment BOMs

- CS01 for material BOMs

- CS51 for standard BOMs

- IB11 for functional location BOMs

Record type 2: one item record (structure BICSP) per item
All BOM item records are assigned to the preceding BOM header, until the next BOM header or session header occurs in the sequential file.

Record type 3: one sub-item record (structure BICSU) per sub-item
All BOM sub-item records are assigned to the preceding BOM item, until the next item header, BOM header, or session header occurs in the sequential file

Exemples ( in the attached spreadsheet )

Exemple 1 : program RCSBI010 -  (Create BOMs using Batch Input) Standard Batch Input program for creating BOM (Bill of material)

Exemple 2 : program RCSBI040 -  (Create BOMs using Batch Input) Standard Batch Input program for creating BOM (Bill of material) with long text

Best Regards

Ziv.

BAdI Implementation for the validation of ‘recipient’ field in PR, PO and Reservation.

                                                                                                                                                          By Jaheer M. Ismail

  In order to check whether user enterscorrect SAP user id in the recipient of purchase Requisition  , purchase order and reservation you can use the following BAdI implementation with below given method. If user does not enter any valid SAP user id and not entered anything in this field then when you try to ‘save’ your purchase Requisition, purchase order and reservation you will get error message.

  In the PR,you can find Recipient field in account assignment Tab.

In the PO, you can find Recipient field in account assignment Tab.

  In the reservation, you can find Recipient field as below

BAdI Name and its method to validate recipient with PR, PO and Reservation:

Transaction code for BAdI implementation is SE18

Logic to validate recipient Field:

Where to write piece of code for validation: Abaper will write code in each method.

Your abaper will write code for the validation of‘ user entered SAP use id’  with table field USR21-BNAME.If user enter
invalid SAP user id, then you get error message like this when you save PR,PO and reservation.

Error Message:Provided Recipient doesn't match with SAP User ID for item &.

This way you can validate your recipient  field in PR, PO and reservation and functional consultant can use this document to write functional specification.

====================================================================================================

Coding part:For PO.

  Here I created one z table( zpo_plant) for putting my plant.This should validate only for certain plants not all plants.

====================================================================================================

method if_ex_me_process_po_cust~process_item.

  include mm_messages_mac . "useful macros for message handling

  break adhummansure.

  data: ls_mepoitem type mepoitem,

        ls_purchase_order_accountings type purchase_order_accountings,

        wa type purchase_order_accounting,

        ls_acc_ref type ref to if_purchase_order_account_mm,

        ls_accounting type mepoaccounting.

  data: lv_bname type usr21-bname,

        lv_werks type zpo_plant-werks.

  ls_mepoitem = im_item->get_data( ).

  if ls_mepoitem-knttp = 'K' or ls_mepoitem-knttp = 'A' or ls_mepoitem-knttp = 'F'

      or ls_mepoitem-knttp = 'Q' or ls_mepoitem-knttp = 'P'.

    select single werks from zpo_plant into lv_werks where werks = ls_mepoitem-werks.

    if sy-subrc = 0.

      ls_purchase_order_accountings = im_item->get_accountings( ).

      loop  at ls_purchase_order_accountings into wa.

        ls_acc_ref = wa-accounting.

        ls_accounting = ls_acc_ref->get_data( ).

        if ls_accounting-wempf is initial.

          message e024(zmm) with ls_accounting-ebelp.

        else.

          translate ls_accounting-wempf to upper case.

          select single bname from usr21 into lv_bname where bname = ls_accounting-wempf.

          if sy-subrc ne 0.

            message e023(zmm) with ls_accounting-ebelp.

          endif.

        endif.

      endloop.

    endif.

  endif.

endmethod.

Introduction

The below article is a short description on Flow of Data between

SAP Material Management (MM) and SAP Supplier Self Service (SUS) and some customizable features of SAP SUS.

In the Plan-Driven Procurement with Supplier Integration scenario the SAP SUS is installed and configured with SAP MM/SRM. Technically, in a classic scenario SAP SUS maybe connected with one or more MM and/or SRM back-end systems.

PO is sent to SAP SUS system, in which supplier can perform the follow-on procurement process, i.e. PO response, ASN, GR response and invoice response.

SAP Supplier Self-Services provides the following processes and functions:

• Vendor Maintenance in SAP Supplier Self-Services
• User Management
• Processing Purchase Orders
• Processing Confirmations
• Processing Shipping Notifications
• Processing Invoices
• Processing ERS Invoices
• Bid Invitations
• Analyses
• Integration of Internet Pricing and Configurator (IPC)

Two scenarios for SAP SUS:  SRM-XI-SUS and MM-XI-SUS.

In SRM-XI-SUS the PO is created in an SRM system locally and sent to SAP SUS. All communication will take place between these two systems via XML messages on both sides with a PI/XI system in between as a mandatory system.

In the MM-XI-SUS scenario the PO will be created in ECC and transferred to SAP SUS. Depending on ECC release there are two different possibilities for this, either the ECC system sends IDOCs or sends XML messages directly. IDOCs will be mapped to XML by PI/XI in all cases, as the SAP SUS system only receives and sends XML messages.

Below is the detailed description on SAP MM ECC sending PO as an IDOC to SUS.

SAP MM ECC sending PO as an IDOC to SUS

SRMSUS BSP Application

SRM SUS Portal or the Vendor Portal is a BSP Application.

The standard BSP application name is SRMSUS, which contains all the standard views provided by SAP.

This BSP Application can be viewed in the Object Navigator (SE80) of the SRM SUS system.

For implementing a customized SRM SUS Portal, this BSP Application is copied and enhanced.

The views are modified as per requirements in the Model View Controller. 

The view changes in ABAP code are done in these controllers.

To understand the flow of data from SAP MM to SAP SUS we shall follow the below mentioned steps:

Sending PO to SAP SUS

Configuring Message Output type

• Create a custom output type for PO to be transferred to SRM SUS.
• Steps to configure output control messages:

1. Condition Table

SPRO/ Material Management/Purchasing/Message/ Output Control/Condition Tables/Define Condition Table for Purchase Order

Select: Purchasing Doc. Type, Purchasing Organization, Vendor

2. Access Sequences

SPRO/ Material Management/Purchasing/ Message/Output Control/Access Sequences/Define Condition Table for Purchase Order

3. Message Type

SPRO /Material Management/ Purchasing/ Message/ Output Control/Message Types/Define Message Type for Purchase Order {NEU}

4. Message Determination Schemas

     4.1. Message Determination Schemas

SPRO/ Material Management/Purchasing/ Message/ Output Control/Message Schema/Define Message Schema for Purchase Order/ Maintain Message Determination Schema

     4.2. Assign Schema to Purchase Order

SPRO/ Material Management/Purchasing/Message/Output Control/Message ne Message Schema for Purchase Order/Assign Schema to Purchase Order

5. Partner Roles per Message Type

SPRO/Material Management/Purchasing/ Message /Output Control/Partner Roles per Message Type/Define Partner Role for Purchase Order

6. Condition Record

SAP Menu/Logistics/Material Management/Purchasing/Master data/Messages/Purchase Order/ MN04 (Create using medium EID Electronic Data Interchange '6')

Significance of Message Output Type

In the created EDI (Electronic Data Interchange) output type of the purchase order, the processing routine contains the program RSNASTED which is responsible for sending the document to the Partner as an IDOC.

The Program RSNASTED is the processing program for each output type, which depending on the definitions for the output mode maintained in the EDI partner profile, will generate and write only one Intermediate Document to a file.

RSNASTED processes entries in the NAST table, which stores an entry for each output record created from application document.

For the created PO, the IDOC created can be checked in IDOC List (WE02).

In case of issues in document transfer, this is the first place to be checked. Green status indicates successful transfer of data from the ECC system.

Creating PO in MM

• Purchase Order is created in SAP MM system and released.
• This is for the professional buying scenario. PO can also be created automatically with reference to shopping carts in the system.

• Assign the created Message Output type with the target system as Partner.
• It is crucial that the created EDI output message is assigned as it is responsible for transferring the PO details to the SUS system.

• Once the PO has been released, this output message type triggers the IDoc which takes the PO details to the SUS system.

SUS Portal

The vendor logs onto the SUS Portal using the User Id provided to them, to check the PO, GR, Invoice notifications, to create ASN, Invoice uploading and to see Payment details.

• New PO notification in Supplier portal

As soon as the PO is created against a Vendor in the ECC system and assigned the EID Output message type, the PO details should be available to the Vendor on his SUS Portal.

The PO details are sent as an outbound IDoc from the ECC system onto the XI/PI system.

In the XI/PI system, this IDoc is mapped into an xml file and sent to the SUS system. Thus, the PO details are visible to the Vendor in his SUS portal id.

• List of POs in SUS Portal

The Vendor will be able to see all the Purchase Orders made against him by the organization in this menu.

Here he can individually go and accept and view details of each of the purchase orders.

Current PO Status displays if it is a new PO or an already accepted/confirmed PO.

• Accepting a PO in Supplier Portal

New POs are to be accepted by the Vendor, confirming that the terms of the PO document are acceptable.

As seen in the screen shot below the Vendor is able to see the PO number, date, company code, Company name and Terms of Payment in the General information layer.

The item code, details, quantity, rate, gross value and delivery date are visible in the item Overview tab.

The fields in these tabs are customizable and the layout is modified as per business requirement.

After accepting the PO the Vendor can then view and update the progress with respect to this PO from the menu screen.

The acceptance of PO by the Vendor can be sent as a PO response to the ECC system via XI/PI.

This is reflected in the PO Confirmations tab in Item detail in ECC.

Advanced Shipping Notice in Supplier Portal

• Creating an ASN in Supplier Portal

Advanced Shipping Notification (ASN) is a notification that is sent by the vendor to the organization when the goods are dispatched.

It generally includes information about the means of transport of the goods and document reference against which it is created.

      Here is an ASN screen in the SUS portal.

    ASN is sent from the SUS to ECC system via the XI/PI system.

• The ASN no. should be displayed in PO conformation control as displayed below.

GR can be done in the system with reference to an ASN.

ASN should also be visible in transaction VL33N.

• Document Flow in Supplier Portal.

Sending GR to SAP SUS

• Goods Receipt is created against the PO in SAP MM

Once the goods are physically received at the storage location, Goods Reciept is done. The details of the GR are required for the vendor to get a confirmation of delivery.

• This Goods Receipt is reflected in SRM SUS Portal

Similar to PO, the GR details are visible

Program that sends GR to SAP SUS

RPODDELVRY is the program that sends the GR document to SRM SUS as an IDOC.

This report allows a synchronization of goods movements for PO and scheduling agreements. It selects all GRs corresponding to POs for vendors in SAP SRM SUS according to the selected vendor classes, including associated cancelations and return deliveries that have not been synchronized with SRM SUS.

The selected goods movements are transferred to the respective target system in SRM SUS using STPPOD.Delvry03-IDocs.
If you start the report as a background job, information can be written to a spool while the report is running.
You can only use this report if the summarization function of the PO history records is not active.
Note that this report is not suitable for the processing of mass movements. The report is suitable for periodic background processing. The system ensures that only one instance of the report is active in the background. The report is not designed to be carried out via batch input.
Synchronization is only possible when table EKBE (procurement document history) is NOT summarized. Batch input synchronization is not possible.

Customizations

Apart from these standard functionalities, Invoice uploading and Payment details can also be added.

Custom BSP pages need to be created for these in the invoice module, which is done in the controller view mentioned earlier.

Supplier can upload scanned copies of the physical invoice in the Invoice screen.

The Payment details of the payment made can be viewed in the Payment details screen.

Uploading Invoice to SAP SUS

The following is a customization, to illustrate the additional uses of the SUS system.

The Vendor can upload the invoice as a scanned copy on the SUS portal, against the PO raised to him. The Invoice amount and date is also entered and submitted as shown below.

Vendor also has the option to upload supporting documents.

Preview of the Invoice uploaded.The Invoice details have to be entered manually at the SAP ECC system in transaction MIRO. The uploaded Invoice is matched against MIGO for invoice verification.

View Payment Details from ECC

The payment details come to SUS sytem from ECC via RFC.

The vendor is able to view the payments made against an invoice raised by him.

The Vendor can view Payments made to him in the SUS portal as shown below.

There can be multiple payments made to the Vendor against the same invoice or have a single payment. This is based on the payment terms maintained against the vendor.

Hope you found this article informative. Please provide your inputs on the same.

Thank you for your time.

I have seen lot of queries regarding automatic stock transport orders generation with reference to stock transport requisitions. I have searched in SCN to find the related document. I am unable to find any document related to Automatic STO creation from STR. I was find the documents related to automatic PO generation but not STO's.

Introduction : Now a days Clients are looking more into Stock transfer from one plant another plant. Stock transport process is commonly used in most of the clients. There are many reasons why client looking into STO process 

1) Sales Order received in Depot plant or branch and manufacturing the goods happens in other plant.

2) Collecting the raw materials or FM CG goods components or packing materials in one plant and transferring to manufacturing plant.

3) Semi finished goods will be prepared at one plant and packing will be happens in another plant.

4) Collecting the perishable materials transferring to other cold storage plants.

Like there are business processes in different industries. Some times Requisitions will be generated through MRP and some times Requisitions created Manually. Some times,there was huge time will take to do huge  materials and some times it is to difficult to search supply plant and receiving plant wise to do STO's.

To avoid this, in SAP we have option to create Automatic STO's with reference to Stock transport requisitions.

Prerequisites :

1) Change default document type from NB to STO Document type in following path.

OLME--> Define default values for document type.

Here need to change default document type (sto document type) for ME21 and ME21N.

2) Configuration should properly maintain for set up STO in following path

OLME---> Purchase order --> set up STO. 

And you have to maintain assign document type, one step procedure, under delivery tolerance.

It is not required to maintain one step procedure. But you need to maintain supply plant and receiving plant with document type.

3) In Material Master, need to maintain automatic PO check in Purchasing view.

4) Source list need to maintain with combination of receiving plant and material and valid period and supply plant (Procurement plant)  and purchase organization.

5) Link should be maintain PR ( in case MRP generated - default document type) document type to PO document type in below path.

OLME--> Purchase order ---> Define document type.

Process :

Once generated the Stock Transport Requisitions ,

In ME59N, enter Purchase requisitions numbers and execute the transactions.

Based on supplying plant, system will generate the STO's.

See Below link , posted by Karoly Taragyia

Explained Trouble shooting on ME59N

ME59N trouble-shooting guide - ERP SCM - SCN Wiki

Sometimes we get these error message numbers: M3 022 - The group data for the material & is locked by &, M3 023 - Plant data is locked by the user &, M3 024- Valuation data for material & is locked by the user &,M3 897 -The plant data of the material & is locked by the user &. That does mean some other user is currently working on the same material. you can't make these messages as warning or you can't switch off these messages from customization. Lets explain how system works internally as the result of these messages externally and how to control these messages.

Exclusive Lock:

Exclusive block is quite like immediate block. When you use a material master during a goods movement transaction, then system will block the particular material master for any other goods movement transaction until you post or leave the current transaction. That means you only can able to post other movement or change master data if the material is not used in any other goods movement transaction. In that case, only one user can post a goods movement, another user can't use the material master for any goods movement transaction. It is used to post the all goods movement correctly, so that the valuation data are updated correctly in the material master and there are no inconsistent during update the quantity and value. But here is a disadvantage : Only one user can post a goods movement transaction at a time, hence this can be a big issue for these types of organizations where a huge of goods movements are posted per day.

In that case, system will issue these above messages as error.

Late Lock:

Late block does mean system will not block immediately or exclusively the material master when another user is using a goods movement transaction for the same material. It will try to block exclusively only when you will go to save the data, so that this material will be blocked for a certain point of time (short time). You need to enter a waiting time to use the late block (by default system will take 10) and it will be as second. Waiting time is a certain number of locking attempts which will created by system before the goods movement posted. It tries to lock the material master data before the posting goods movement, so that all posting would be consistent (correct). If any other user use a goods movement for the material master, then system will wait for a certain time and then again tries to set the block.

Shared Lock :

Shared lock does mean to share the locking activity between goods movement and material master. Suppose, an user is processing a goods movement transaction, then you can able to change the material master data without valuation related and inventory management related data (such as material price, valuation category, unit of measure, indicator for batch determination etc). If you go for change a material master and you have done some changes and before pressing save another user has posted a goods movement in the meantime, then system will refuse your entry and system will through a message "MM 628 - The field cannot be changed at the moment due to a goods movement", and you need to leave the transaction and do it again. If another user is posting a goods movement transaction and during the time you are trying to change some data related to the valuation or inventory management, then system will issue the message "M3 024 - Valuation data for material & is locked by the user &". But you can still able to save the changes of other data (like as material description, material group, division, tick option of automatic PO, source list. Anything not related to valuation or inventory management). The only disadvantage of the share lock, you can't change these fields whose are related to valuation and inventory management level.

Shared lock will work when you are using the late lock. System will refuse the share lock if you set the the locking activity as "Lock Exclusively" in customization.

Customization :

There are two customizations to use these above facilities. In one customization, you have to set the locking activity as either "Lock Exclusively" or "Late Lock", and in other customization you need to set the "Shared Lock".

In the IMG path SPRO - IMG - Materials Management - General Settings for Materials Management - Set material block for goods movements , you can set the locking activity for goods movement transaction or you can use the t-code OMJI. Here you can choose your desire option:

(Note: You may can see different screen for IMG path and transaction OMJI, but these both are same)

To use the shared lock function, you need to go to the IMG path SPRO- IMG - Logistics-General - Material Master - Basic Settings - Make Global Settings or you can use t-code OMT0. Here you can set the indicator as per your desire requirement :

Material block during Invoice posting :

You can also block material master record during invoice verification, you can use 3 methods for this blocking activity:

1. All materials will be blocked during invoice posting (Material is blocked at first read) :

In this activity, if you will choose a purchasing document for invoice posting with regards to some materials, then these materials will be blocked for any changes related to valuation data level.

Suppose, you are processing an invoice which contains a material, then this material will be blocked for valuation data level. You will receive an error message "M3 024 - Valuation data for material & is locked by the user &".

2. Particular material blocked during invoice posting (Material is blocked when invoice is simulated/posted) :

In this activity, only these materials will be blocked whose stocks to be updated (for the reason of any variance of GR value and invoice value).

Suppose, you are processing an invoice which contains a material, and during simulation, there are some value goes to the material account (inventory account), then system will block the material at valuation data level. System will issue the message "M3 024 - Valuation data for material & is locked by the user &".

3. Material block during direct posting :

In this case, when you will use the tab material in MIRO during posting the invoice, then system will block the material at valuation level immediately.

If you are using the invoice and goods movement transaction parallel, then you should choose the option "Material is blocked when invoice is simulated/posted".

Configuration can be controlled by the path SPRO - IMG - Materials Management - General Settings for Materials Management - Set Up Material Block for Invoice Verification :

Select you desire option from these 3 methods.

Reference help documents:

Late Exclusive Material Block (Enqueue) for Goods - Release notes for release 3.0D - SAP Library

Material Block (Material Enqueue) for Goods Movements - Inventory Management and Physical Inventory (MM-IM) - SAP Librar…

SAP Notes:

322989 - Late block: Number of blocking attempts

1166612 - Locking error for material during parallel goods movements

1985306 - Performance guide for goods movements

1766569 - VL02N locking issue: M3024 raised

KBA

1744780 - Error message M3024 during Invoice Verification process

Business Scenario:

We execute the report MB5B to check stock as on posting date along with we can check the stock analysis from the same transaction code. We choose the tick option of “Totals Only” to see the sum of these columns ‘Opening Stock, Total Receipt Quantities, Total Issue Quantities, Closing Stock. If we don’t select the totals only, then we can able to see all movement type’s line items with regards to our selection criteria. Here we can see all movement types which is related to all modules (MM SD QM etc.). To see line items for some specific movement type (e.g. how many quantity has posted with regards to the movement type 101,105,109 etc.), you need to choose the filter option. But with the help of movement type group, you can see selected line items by choosing the movement type group and you can see only these line items which have been grouped under the selected movement type group.

Suppose, you need to find line items for these movement types which are causes of goods issue. We know these movement types (suppose 201, 221, 333, 551 etc.) are used for goods issue. It may be able to achieve this by filtering these movement types from MB51 or MB5B. SAP has given the facility of movement type group, so that you do not have to choose the movement type manually, You just need to assign the movement type to movement type group, then you can able to see all line items with regards to movement type.

Assignment:

It’s a very simple configuration that you need to do in IMG activity. You just need to assign the movement type to movement type group in this IMG path SPRO - IMG - Materials Management - Inventory Management and Physical Inventory - Reporting - Group Movement Types for Stock Lists.

Here, choose your movement type and assign the movement type group as per your requirement. Movement type group is a free text field; you can enter any text in this field (as quite same like as account modifier for movement type). Do it for these movement types which you want to see in MB5B stock analysis report when you will choose the movement type group. You can also select your custom movement type (as per your business requirement). System read the table T156S for the movement type. You can’t able to create any entry here. All movement types are created from OMJJ transaction will be updated here with blank movement type group automatically.

(Note: You will be able to see a warning message as “Do not make any changes (SAP entry)”. Read the message carefully and do that accordingly which is explained in the procedure section.)

Result:

Run the report MB5B without choosing the option ‘Totals only’. You can see all line items for all movement types. Now choose the movement type group from the screen layout as below:

Here, the field name will be ‘Group f. Stock Anal.’ (As you can see the above screen shot)

Then you can see the field movement type group in the output list. Also here you can see a default value as ‘REST’ for those entries which haven’t assigned to any movement type group. That means if you will not assign any movement type group with regards to movement type in IMG, then you can see the value ‘REST’ for these line items in this output list. It is designed by system.

Now you can see your selected movement type’s line items by sorting or filtering the movement type group. Just filter the tab movement type group as per your assigned group.

Conclusion:

This is just an extra facility from SAP to check the stock analysis and it is only used for reporting purpose at the section inventory management. You can’t use this movement type group in selection screens. You can’t use this facility in MB51 transaction; it is only applicable for MB5B stock analysis transaction. You can keep the output layout by saving the adjusted layout, if you want to see the same later. The assigned value of movement type group is stored in table T156Q as per movement type. You can also select special stock wise movement type during the assignment of movement type group. You should not select specific movement type in MB5B in selection field as because of incorrect result. If you will select any specific movement type in MB5B, then system will through a warning message “If there are restrictions acc. to movement type, results may be incorrect”. So you need to run the report without selecting movement type and then use the movement type group to see the stock analysis with regards to your required movement type.

SAP help document : Group Movement Types for Stock Lists

Purpose:

The aim of this document is to provide an understanding of the Freight cost capture on KG basis with reference to Inbound Delivery / Advance Shipping Notification.

Process:

Material Master Settings:(Tcode - MM02)

The Gross weight has to be maintained at Basic Data 1 in material master along with weight unit, here the gross weight 30 KG taken for example.

Creation of Purchase Order: (Tcode - ME21N)

Purchase Order has to be created with Confirmation Control Key 0004 Inbound Delivery, here 100 KG taken for example.

Creation of Inbound Delivery / Advance Shipping Notification: (Tcode - VL31N)

Complete Purchase Order quantity taken for IBD and the total weight has been calculated based on Material Master and Delivery (30 KG X 100 KG = 3000 KG).

Creation of Condition Record: (Tcode - TK11)

Go to the transaction TK11 and pass the condition type FB00 for Weight basis, here the key combination take for Transporter, Shipment Type and Shipment Route. Here Rs.55 taken per KG for Route 1, Rs.60 for Route 2 and Rs.30 for Route 3 respectively.

Creation of Shipment: (Tcode - VT01N)

Use the shipment type 0010 Inbound Shipment with corresponding Transport Planning Point for Shipment Creation, pass the required Inbound Delivery number and execute.

Pass the Transporter name along with Shipment route and Type, system will calculate the freight cost automatically based on condition record.

Here Gross quantity is 3000 KG and net Value is 165000 (3000 X 55).

Creation of Shipment Cost: (Tcode – VI01)

Create shipment cost document with reference to shipment number.

Change Shipment Cost: (Tcode – VI02)

Pass the shipment cost number and tick Transfer check box for auto Purchase order creation.

Service Purchase Order has been created in background and you can see the Material Document Number and Service Entry Number in Purchase order history. 

Configuration:

OLML – Shipping - Basic Shipping Functions – Routes - Define Routes - Define Modes of Transport

We have to assign this mode of transport into shipping type and we can define the same as per business requirement, also it will be easy to monitor whether the material transfer by Road or Air.

OLML – Shipping - Basic Shipping Functions – Routes - Define Routes - Define Shipping Types.

We are using this Shipping Type is on of our key combination and we can set different prices based on shipping type through condition record.

OLML – Shipping - Basic Shipping Functions – Routes - Define Routes - Define Routes and Stages.

We can define the route and stages based on the distance where the vendor located and the transportation price will be differ based on the distance, we are using the route also on of our Key Combination in condition record.

OLML – Transportation – Shipments - Define Number Ranges for Shipments.

Set up new number ranges for Shipment document.

OLML – Transportation – Shipments - Shipments - Maintain Transportation Relevance - Maintain transportation relevance for delivery types.

Kindly activate the below check box then only the we can use delivery type "EL" for transportation process.

OLML – Transportation – Shipments - Maintain Transportation Relevance - Maintain transportation relevance for delivery item types.

Kindly activate the relevant Item category for the delivery type "EL" for transportation process.

OLML – Transportation – Shipments - Define Number Ranges for Shipments - Maintain Transportation Relevance - Maintain transportation relevance for routes.

The activation has to be done for relevant route then only the route can be used for shipment.

OLML – Transportation – Shipments - Define Shipment Types.

Shipment Type having various control for transportation process like Output determination procedure, number ranges etc... Below proposal screen we are using the weight unit is "KG" since we are calculating the transportation cost on KG basis.

OLML – Transportation – Shipments - Configuration of Transportation Processing for Forwarding Agents.

This configuration mainly using to identify the service agent who are involving into freight forwarding process, we are using this forward agent also on of our key combination in condition record.

In second screen you can come to know the assignment process of Transportation planning point with shipment type, when ever we use the transportation planning "CH" system will consider the shipment type "0010 Inbound shipment".

Shipment Cost:

OLML – Transportation - Shipment Costs - Shipment Cost Document - Define Number Ranges for Shipment Costs.

Here we can define own number ranges for shipment costs, when creating a shipment cost document, a unique number is generated as per this configuration.

OLML – Transportation - Shipment Costs - Shipment Cost Document - Shipment Cost Types and Item Categories.

Here we can define the shipment cost types and item categories that contain all important control features for the shipment cost document and also we can assign the valuation class makes it possible to post the values of services of the same service category to different accounts.

OLML – Transportation - Shipment Costs - Shipment Cost Document - Shipment Cost Relevance and Default for Shipment Cost Type.

Here we can assign the shipment cost types to the shipment types and set an indicator to show whether the cost type is relevant to shipment costing, this setting has to be done for every cost type in every shipment type.

OLML – Transportation - Shipment Costs – Pricing - Pricing Control - Define Price Dependencies (Condition Tables)

A table where the key fields are data combinations for which messages are triggered and there is a condition record for each data combination, here we craeted table by using the Service Agent, Shipment type and Route as a key combination.

OLML – Transportation - Shipment Costs – Pricing - Pricing Control - Define Condition Types.

Since we are looking this process to calculate transportation cost for Weight basis, here we have taken standard Condition type FB00 is using for Gross weight.

In second screen you can see the calculation base "A- Delivery" if it is A then the total weight will be consider from delivery header level.

OLML – Transportation - Shipment Costs – Pricing - Pricing Control - Define Access Sequences.

As you aware an access sequence is a search strategy which uses to search for condition records valid for a condition type, here we have taken MAKT and the table assign to the same.

OLML – Transportation - Shipment Costs – Pricing - Pricing Control - Define And Assign Pricing Procedures - Maintain pricing procedure.

We can set the pricing procedure as per the requirement by using above condition type.

OLML – Transportation - Shipment Costs – Pricing - Pricing Control - Define And Assign Pricing Procedures - Define pricing procedure determination for shipment costs.

All the shipment is allocated to a transportation planning point for transportation planning. It helps to determine responsibility for transportation processing during which it can be used as a selection criterion, in order to create a list of shipments to be processed, say for example one planing point can be used for Road and another for Air like wise.

Finally all Item determination procedure group, service agent procedure group and shipping type procedure group which has been done above configuration need to be assign with Pricing procedure. 

OLML – Transportation - Shipment Costs – Settlement - Assign Purchasing Data.

Finally we need to assign the Transportation planning point with shipment cost type, purchase organisation, purchasing group and plant for auto purchase order creation. 

Background

Here now an example how to fast upload Characteristics to SAP using excel from one  file without ABAP code

The following approach can be alternative to LSMW  or  using  transaction BD91 which often requires some basis customization.

This solution provide excel which generates flat file which is uploaded to Standard Batch Input program for creating Characteristics ,This can save development of designated ABAP programs which writes data to a sequential file in the format required by the ABAP program RCCTBI01.

How to do it ? (see exemple videofor CT01 transaction)

- First Download the Excel Characteristics tool here

- Then follow step1-6 as described in these screen shots
 

Step 2 : Fill the  template using structures (BGR00,BISMT,BISZW)

Comments are welcome.

Regards,

Ziv

Hi SCN Members,

I would like to share my knowledge on Moving average Price.  Before going to this we should know about the Price Control.

Sap offers two methods of Price control: 

1) Moving Average Price (V)    

2) Standard Price. (S)

The method to be used is identified on the material master level, thus different materials can use different methods with in plant.

SAP recommended that, Standard price usually used for finished or semi-finished material.

Moving average price are used mainly for Raw Materials and External Purchases.

The Price of external procured materials varies based on Market, will reflect the current market cost. Because of this reason we will use the Moving average price for External procured material like raw materials and Trading materials...etc.

While going to new client implementation, for moving average price will get updated based on initial stock upload with Value. But for Standard price Control S will be updated based on standard cost estimation.

Different ways to find Moving average Price Calculation on selection Date:

They are different ways to check moving average price calculation. If you need to find the Logic to develop the Report to see Moving average price on period or day basis- Need to find Logic for this.

1. 1)    By using Formula
2. 2)    From Standard Reports
3. 3)    From Multiple tables Mapping
4. 4)    From Info Structure tables

1. 1) By using Formula :

When material is subject to moving average price control, the system values for goods movements in following way

Using above formula we can calculate Moving average price. Below explained with example.

Example:

1. 1)    20.04.2015 Goods Receipt Quantity 100 Kg and the value of Goods Receipt as 1200 Rs.
2. 2)    21.04.2015 Goods Receipt Quantity 90 kg and the value of Goods receipt as 1100 Rs.
3. 3)    24.04.2015 Goods Issue Quantity 50kg
4. 4)    29.04.2015 Goods Receipt Quantity 110Kg and the value of Goods receipt as 1600.

Now I need to find the moving average price on 24.04.2015. Using above formula we can find this.

The moving average price on 24.04.2015 is 12.11 and on 29.04.2015 is 13.18.

1. 2) From Standard Reports :

In standard, we have standard report can view the moving average price.

T-code: S_P00_07000139

Here we need to work out on date basis. If more than one entry on the date then you have to pick the last entry Moving average price.

You can find moving average price Period wise also.

T-code: MC.1   / MC.9

Here we need to work out on formula.  i.e.; Total valuated value / total valuated stock.

Enter Period and other required fields and execute the Program.

You will get the total valuated value and total valuated stock.

Total valuated stock value = 86500, Total valuated stock = 3250

=86500/3250 = 26.62.

If you need you can compare MC.1 and S_P00_07000139.

In S_P00_07000139, you have to give 30.04.2015 for month of period 04.2015.

Same you can compare with MB5B- Total receipts - total issues with quantity and value.

1. 3)    From Multiple Table Mapping :

We can write logic to get the report for moving average price on selection date.  As know everybody we can get latest price from MBEW table. But how we can see when the price was updated and how it was updated can be get values from CKMI1.

Tables: MBEW, CKMI1

Logic:

1. 1)    Pass Material and valuation area (plant) in MBEW table and pick the value of Prod CostEst.No. (KALN1)
2. 2)    Pass Prod Cost Est no into CKMI1 table – filed name Cost estimation no (KALNR) and pass year
3. 3)    Check the values of quantity and amount and moving average price.

The moving average price will be update when the next accounting entries updated. Example: if you are checking on 30.04.2015 and next entry updated at 01.05.2015 then you should see moving average price on 01.05.2015 and it will be the moving average price on 30.04.2015

Here see above entries. On 30.04.2015 the moving average price is 26.62 which is updated on 04.05.2015.

You can calculated summation of all the amount / summation of all the Quantity up to date.

If you want to see on 30.04.2015 then (Qty -> 1000+1500+750 = 3250) and (Value-> 25000+45000+16500 = 86500) = 86500/3250 = 26.62.

1. If you want to see latest price when it was updated means -à see the last date entry on date in CKMI1 and check in MBEW for latest price.
   1. 4) From Info structure Table :

S031 -Material movement data on monthly basis

In Standard we have S tables which is related to LIS structures. The below S Table which is related to Inventory stock and price. From this you can find the moving average price on date. We can call as info structure table.

Table: S031 – information structure for Inventory stock and price on period based on date based. While updating the values you should select date basis (daily basis).

For better practice you can copy from S031 to S931 and update the values in S931 on daily basis.

In this table, will get valuated receipt stock and valuated receipt value and also valuated issue stock and valuated issue value.

Summation of all valuated receipts quantity and value as well as valuated issue quantity and value from up to date all entries (selection date).

Moving average price = (total value receipt – total value issues)/ (total quantity receipt – total quantity issues).

You can see below link regarding LIS written by PRASOON.

http://scn.sap.com/docs/DOC-50821

http://scn.sap.com/docs/DOC-50822

http://scn.sap.com/docs/DOC-50823

For best we can see below link

http://www.erpgreat.com/materials/mc-9-correction-and-comparison-with-gl-accounts.htm

Related SAP Notes:

Note 483735 - Self-defined info structures with reference S031, S032, S039

Note 512416 - LIS | Stocks in the past

https://service.sap.com/sap/support/notes/512416

Note: Sometimes you will not get correct moving average price. Why because if there is any unplanned delivery cost or value variance posted to stock account while doing MIRO. These values will be posted to stock account and Quantity remains same. In this case you have to consider these values from BSEG table.

When attachment is added to PR and when we create Purchase Order (PO) based on Purchase Requisition (PR), then all the attachment attached to PR line Item will be copied from PR to PO automatically. But if we are using BAPI to create PO, then attachments won't get transferred to PO. When I searched for such requirement, I did not get any solution. Hence I have designed and sharing the same which might be useful for few members. Below code will help to transfer the DMS document id (attachments) from PR to PO while using BAPI to create PO . This function need to be called after committing "BAPI_PO_CHANGE" OR  "BAPI_PO_CREATE1" BAPI. PR number will be passed as input to this function module.

FUNCTION zm_copy_att_from_pr_to_po.

*"----------------------------------------------------------------------

*"*"Local Interface:

*"  IMPORTING

*"     VALUE(I_BANFN) TYPE  BANFN

*"  TABLES

*"      T_RETURN STRUCTURE  BAPIRETURN

*"  EXCEPTIONS

*"      NO_PURCHAING_DATA

*=============================================================================*

*-----------------------------------------------------------------------------*

* Function Module  : ZM_COPY_ATT_FROM_PR_TO_PO                                *

* Author           : Sasikanth SM (XSSM)                                      *

* Date             : 05/15/2015                                               *

* Thread Manager ID:                                                          *

*-----------------------------------------------------------------------------*

* Type of Program  : Function Module                                          *

* Purpose          : This function will copy the DMS document id attached     *

*                    to PR and link the same to PO                            *

* Transport Req    :                                                          *

*-----------------------------------------------------------------------------*

  DATA: w_drad          TYPE drad,

        i_drad          TYPE TABLE OF drad,

        i_dradn         TYPE TABLE OF  drad_n,

        w_dradn         TYPE drad_n,

        w_eban          TYPE eban,

        i_eban          TYPE TABLE OF eban,

        w_bapireturn    TYPE bapireturn.

  DATA: lv_new_objkey     TYPE drad-objky,

        lv_old_objkey     TYPE drad-objky.

  CONSTANTS : c_eban      TYPE dokob  VALUE 'EBAN',

              c_ekpo      TYPE dokob  VALUE 'EKPO',

              c_x         TYPE c      VALUE 'X',

              c_i         TYPE c      VALUE 'I',

              c_e         TYPE c      VALUE 'E'.

*=============================================================================*

* Get the PR details based on the input passed.

  SELECT * FROM eban INTO TABLE i_eban

    WHERE banfn = i_banfn.

  IF sy-subrc NE 0.

    RAISE no_purchaing_data.

  ENDIF.

  LOOP AT i_eban INTO w_eban.

*   Generate refference object (PR) key

    CONCATENATE w_eban-banfn w_eban-bnfpo INTO lv_old_objkey.

*   Generate new object (PO) key

    IF w_eban-ebeln  IS NOT INITIAL.

      CONCATENATE w_eban-ebeln w_eban-ebelp INTO lv_new_objkey.

    ENDIF.

    CHECK lv_new_objkey IS NOT INITIAL.

*   Get the Document key's of PR Line Item

    CALL FUNCTION 'DOKUMENTE_ZU_OBJEKT'

      EXPORTING

        key           = lv_old_objkey

        objekt        = c_eban

      TABLES

        doktab        = i_drad

      EXCEPTIONS

        kein_dokument = 1

        OTHERS        = 2.

    IF sy-subrc NE 0.

      CONCATENATE text-001 lv_old_objkey  INTO   w_bapireturn-message.

      w_bapireturn-type      = c_i.

      APPEND w_bapireturn TO t_return.

      CONTINUE.

    ENDIF.

*  Populate i_dradn itab from i_drad

    LOOP AT i_drad INTO w_drad.

*   Assign PR Item document to PO Item

      MOVE-CORRESPONDING w_drad TO w_dradn.

      w_dradn-dokob = c_ekpo.

      w_dradn-objky = lv_new_objkey.

      APPEND w_dradn  TO i_dradn.

    ENDLOOP.

    CHECK i_dradn[] IS NOT INITIAL.

*   Map the PR document key to PO Line Item

    CALL FUNCTION 'DOKUMENTZUORDNUNGEN_BUCHEN'

      IN UPDATE TASK

      EXPORTING

        ob      = c_ekpo

        objky   = lv_new_objkey

      TABLES

        savdrad = i_dradn.

*  Commit the changes

    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'

      EXPORTING

        wait = c_x.

    REFRESH: i_drad, i_dradn.

    CLEAR  : lv_new_objkey, lv_old_objkey, w_drad, w_dradn, w_eban.

  ENDLOOP.

*=============================================================================*

ENDFUNCTION.

News --- News --- News --- News --- News --- News --- News --- News --- News --- News --- News --- News --

  Service efforts for both packages have just dropped tremendously, and made implementing the scope of these RDS a lot more affordable.

  Ask your SAP account executive  about integration services today

ws --- News --- News --- News --- News --- News --- News --- News --- News --- News --- News --- News ---

SAP customers can now integrate their procurement applications with Ariba more easily than ever.

Free of charge for SAP customers and partners, two new and improved Ariba integration rapid-deployment solutions (RDS) have been released on the SAP Service Marketplace and can  be downloaded by SAP customers and partners for immediate use:

• Ariba Procure-to-Pay Integration rapid-deployment solution (P2P RDS)http://service.sap.com/public/rds-aribap2p
• Ariba Network Integration for SAP Business Suite rapid-deployment solution (ANI RDS). http://service.sap.com/public/rds-ariba

In addition to the free packaged setup guides for prescribed integration scenarios, SAP and some qualified partners such as Deloitte also offer tailored support to deploy the RDS integration (at a fee). What’s the catch? Companies who wish to integrate SAP Business Suite (focusing currently on SAP ERP MM and SRM classic) and Ariba do need to have a configured ERP environment, and of course an Ariba subscription.  But, hey, the content for both RDS is available for free, making for some well-guided DIY integration for customers with in-house integration expertise.

The P2P RDS caters to SAP customers who would like to offer their employees a great user experience for self-service procurement in a modern system of engagement. Ariba procurement documents will be exchanged with suppliers on the Ariba Network, and replicated to SAP MM as the system of record. With SAP Best Practices™ and proven methodology, the P2P RDS extends SAP MM into Ariba P2P, guides you through the setup, configuration, and master data synchronization among the systems, and secures document transfers from Ariba P2P back into MM. Test scripts provided in the RDS help ensure readiness for go live.

Download the P2P RDS here: http://service.sap.com/public/rds-aribap2p         

The ANI RDS caters to SAP MM and SRM classic customers to automate collaboration with their suppliers in respect to SAP MM POs and logistics invoices on the Ariba Network. The ANI RDS provides SAP customers with a set of guides to integrate their ECC 6.0+ with Ariba within a few weeks. Best practice guides show how to configure MM correspondence with suppliers on the Ariba Network for highly automated, touchless electronic processing of digitized procurement documents from Purchase Order to invoicing and payment. Optionally, Ariba Discount Management can be activated. Add-on installation, SSL configuration, and optional middleware setup for HCI or NW PI, are documented for easy, self-guided implementation. Test scripts ensure readiness for go live here as well.

Download the ANI RDS here: http://service.sap.com/public/rds-ariba  

Check out how to access and use the content here: Ariba Network Integration for SAP Business Suite Rapid-Deployment Sol…

Customers are encouraged to download the package from the links above, review the prescribed integration scope items, and contact their SAP account executive or integration partner for support.

Check back in here soon for new e-learnings on Ariba integration.

Contacts:

For P2P RDS content please contact peter.huyen@sap.com.

For ANI RDS content please contact andreas.muno@sap.com.

For RDS integration services by SAP please contact jason.didday@sap.com

We know unit of measure is a vital thing which is used in material master, purchasing document and inventory management etc.  I hope I do not need to elucidate about what a unit of measure is and where it is used. There are lots of SAP help document where you will find all type of details for unit of measure. As we know, there are certain type of unit of measure is used in material master, purchasing document and inventory management like as Base unit of measure, Order unit, Order price unit, stock keeping unit, even you can find more in this SAP help document Units of Measure - Material Master (LO-MD-MM) - SAP Library

Here, I’ll explain how it is used in a purchasing document, from where it can be defaulted, what the priority is for fetching this unit of measure and how the calculation of conversion will be calculated during a creation of purchasing document and goods movement.

As we know, in purchase requisition, we can only have the base unit of measure as unit of measure (EBAN-MEINS). We can’t use any kind of alternate unit of measure (MARM-MEINH) or order unit (MARA- BSTME) in purchase requisition. It is SAP standard design and we can’t change it.

There is another unit of measure field in purchase requisition that is called PO unit (EBAN-BMEIN), this field is used to default the order unit during creation of purchasing document (e.g. Contract, RFQ, Purchase order or Schedule agreement). This field value if coming from source list maintained for the material in ME01 (EORD- MEINS). If there are no source list, then system will pick the unit from source of supply (can be an agreement or a purchase info record).

In this source of supply tab in purchase requisition, you can see multiple order units with regards to same info record. It is depend upon your selection of the tick option “Source determination” (MEREQ_TOPLINE- KZZUO), if you tick this option, then you can’t see multiple order units in this tab, system will fetch only the order unit which is maintained in info record (EINA-MEINS). But if you do not tick this option, then you can able to see all unit of measures which are maintained in your info record condition tab (in case of Variable Purchase Order Unit in active (as 2 - Active with own price) and condition is maintained as per this document Create Info Record for different Order Unit)

In a purchasing document, we can use an alternative unit of measure which is defined in material master (if you are using material master in your purchasing document). If you are not using any material master (for account assigned purchasing document), you need to enter the order unit manually for purchase order line item.

There are some priorities for the order unit (EKPO-MEINS) from where system will fetch the unit of measure. Let’s explain how system reads the unit of measure and how the conversion is calculated during purchasing document creation.

There are 3 ways from where system can fetch the order unit for a purchasing document:

1. Reference document
2. Purchase info record
3. Material master

First priority will be always reference document. If you are creating a purchase order with regards to a contract, then system will always copy order unit (from EKPO-MEINS) and order price unit (from EKPO-BPRME) and all conversion factors from contract and you can’t able to change this order unit. In that case, system will make the order unit as grey mode, but still you can change the order price unit. System will ignore all other reference (like purchase info record or material master).

If you are using a purchase requisition as reference, then order unit will be copied from PO unit (EBAN-BMEIN, which is exists in source of supply tab), here system will allow you to change the order unit. If this field (EBAN-BMEIN) is blank, then system will fetch the order unit from purchase info record.

Second priority will be purchase info record. If you are not using any reference purchasing document, then system will always copy order unit (from EINA-MEINS) and order price unit (from EINE-BPRME) and all conversion factors from purchase info record. In that case, system will allow changing both order unit and ordering price unit.

==>Note: You can always change the order unit in info record (EINA-MEINS) as per your requirement, but system will not update any old purchasing document which was already created by using this info record. It will effect only for new purchasing document.

Third priority will be material master record. If you are not using any reference document or any purchase info record, then system will fetch the order unit and conversion factor (from MARM table) from material master (in that case, order price unit will be same as order unit). First, system will search for the order unit maintained in material master (MARA- BSTME), if there is no order unit, and then system will pick the base unit of measure from material master (MARA- MEINS) as order unit in purchase order line item.

==>Note: If you are using Variable Purchase Order Unit as active (1 or 2), then system will always propose base unit of measure as order unit in purchasing document even though you maintained a different order unit. If you active Variable Purchase Order Unit, then system will allow you to change order unit as per your requirement, you just need to maintain the conversion factor in material master. Remember, if you change the order unit manually, then system will not change order price unit automatically, system keeps the existing order price unit, you need to change it manually also.

For the conversion factor, system will always fetch the conversion factor accordingly with regards to the reference document (if any). In case of batch specific conversion, system will ignore all other conversions. The prerequisite is your order unit has to be matched with batch unit.

At the time of creating a service purchase requisition or purchasing document (by using item category D), system will use a default unit of measure (T165-PER_MEINS) which is defined in ML91 and you can’t change it further. For a service requisition or purchasing document, system will always consider the unit of measure which is entered in service tab (ESLL- MEINS) for further process. By the way, changing the order unit (EKPO-MEINS) is controlled by field selection of item category D (field selection PT9F).

==>Note: As of release 606, system will change automatically the purchase order line item’s order unit (EKPO-MEINS) by service tab’s order unit (ESLL-MEINS).

In case of creating an intra-company stock transport order (by using item category U and document type UB), system will not consider the order unit. System will fetch the value from unit of issue (MARC- AUSME). Causes of this behavior, plant to plant transfer is not correspond to purchasing, it is quite comes under transfer posting; hence system will not pick the order unit which is maintained in material master. If there is no value defined in this field (unit of issue), then system will fetch the base unit of measure as order unit in stock transport order. In case of using Variable Purchase Order Unit (1 or 2), system will consider base unit of measure as order unit in stock transport order even though you have maintained a different unit in the field unit of issue. For inter company stock transport order (using document type NB), system will consider order unit as per normal purchase order.

==>Note: This field (unit of issue) value can be stored in material master (MARC-AUSME) different with regards to plant and also by using unit of issue in material master (MARC- AUSME), system will also consider this unit of measure as ‘Component unit of measure’ in CS01 (STPO-MEINS).

Remember, system will never change any conversion factor or order unit in purchasing document automatically. If there are any changes in material master or info record after a purchasing document created, then you have to create a new purchasing document to bring this new effect. If you carry out any further process (e.g. goods receipt) for any existing document, then system will carry the old order unit or conversion factor for further process.

During goods receipt with regards to a purchase order or schedule agreement, system will always propose you order unit as ‘Unit of Entry’, but you can always change this unit as per your requirement. You just need to be sure that conversion factor of this new unit is maintained in material master; system will pick this conversion from material master. In the same way, during transfer posting, system will allow you to enter different unit of measure in the field ‘Unit of Entry’, system will take the conversion factor from material master. If you will not enter any unit of entry during transfer posting, then system will pick the base unit of measure as unit of entry. For valuation during goods receipt, system will always use the order price unit for GR/IR clearing account’s value and base unit of measure will be considered for stock account line item posting. During physical inventory document, you have the option to enter Unit of entry in MI04 (during count) and MI10 (Create List of Differences w/o Doc.) manually. System will always propose the base unit of measure in this field (Unit of entry (physical inventory)) (ISEG-ERFME), But you can change it from default to any other as per your requirement. You just need to be sure that the conversion factor is maintained in material master. System will take the conversion from material master (MARM table). Once you will enter a different unit of entry in this field, system will calculate the quantity for Base Unit of Measure (ISEG-MEINS) automatically as per maintained conversion in material master.

==>Note: Even though you are using any different unit as ‘Unit of Entry’ during a goods receipt or transfer posting or physical inventory process, system will always update stock as per stock keeping unit (which is base unit of measure). System will update all unit of measures in MSEG table (ERFME = Unit of Entry, MEINS = Stock keeping unit, BSTME = Purchase order’s order unit). Conversion factor will be used as ERFME to MEINS will be picked from material master (MARM table); BSTME to MEINS will be picked from purchasing document (EKPO table). In MB52, you can only see the unit for stock as per base unit of measure, but in MMBE, you can see the stock with different alternative unit of measure by selecting the unit in the field ‘Display Unit of Measure’. In that case, system will calculate the conversion from material master. If you are changing the alternative unit of measure frequently (after done some posting), then you may can see wrong data by using this option, as because system will always take the current conversion from material master.

During sales order creation, system will propose the Sales unit (MVKE-VRKME) from material master for sales order line item (VBAP- VRKME), if the field Sales unit (MVKE-VRKME) is blank in material master, then system will pick the base unit of measure as sales unit. Here, system will allow you to change the unit of measure for sales order item (VBAP- VRKME); you just need to be sure that conversion factor is maintained in material master. You can maintain a different conversion factor for this sales order line item. Once you will change the Sales unit, then you need to change the Condition unit in the document manually. System will not change the Condition unit in the document automatically.

==>Note: In material master, you can use different sales unit as per combination of Sales Organization and Distribution Channel. You may be able to restrict changes for this field via screen variant.

Here is some reference documents for more details about unit of measure.

SAP help documents:
Units of Measure in Purchase Orders - Purchasing (MM-PUR) - SAP Library

Units of Measure in Inventory Management - Inventory Management and Physical Inventory (MM-IM) - SAP Library

Reference OSS notes (KBA and Recommendation note):

187511 - Redesign quantity conversion

1836255 - Units of Measure used in the Valuation of WRX and BSX

77525 - Quantity unit conversion in inventory management

1772735 - Stock Report with Alternative Unit of Measure

1981710 - Wrong unit of measure in RFQ (reference for quotation )

1795967 - If the requisition is generated via MRP the Order unit is not copied from the source list

445239 - ME56/ME57-Source Overview displays numerous OUn

2027096 - Service Purchase Requisition UOM is defaulted and can not be changed at item level.

138767 - Changing the base unit of measure

1597737 - Purchasing Order unit is not defaulted into UB Document type

1994263 - Change of order unit does not update condition unit in Info record

2100007 - Fields about PO Conversion of Order Unit to Base Unit can not be set as editable

1980679 - Why the field 'Unit of Issue' of the supplying plant is taken in STO?

SAP OSS notes for program correction regarding unit of measure:

1304204 - Purchase requisition services, no ISO unit of measure

885453 - ME21N: Message 06 480 for PReq without material number

1662759 - Order Unit not derived while creating Outline Agreement

872955 - ME5xN: F4 help for units of measurement in item overview

1115005 - ME51N: Check against the unit UoM of the source of supply

1128924 - Quantity conversion doesn't happen from PR->PO

1714849 - MIRO: Qty conversion in base unit of measure (ACCTIT-MENGE)

1607326 - ME11: Order Unit not taken from material master

1719704 - ME12: Wrong conversion factor after order unit change

1068670 - Units of measure using BAPI_SAG_CREATE/BAPI_CONTRACT_CREATE

Introduction

This is my first document so I will be improving this document based on your feedback. I thought to create this document to share my latest integration expect between WM and MM for Goods receipt and reversal.

I assume that you already configured your WM system and other WM settings required to process the goods receipt using inbound deliveries.

MM and WM Integration

Master Data- You must have WM views created for material master

Master Data Used in this process

- Material Master

- Vendor Master

- Info Records (Optional)

- Storage Bins- Storage Bins is master data for managing stocks in WM

Key Document Definitions

Purchase Order- Legal document issued to vendor to supply goods or services. In this case goods

Inbound Delivery- Notification for shipping or Notification receiving of goods

Transfer Order- This is WM document. It is used to give instruction to WM user to perform action. Normally it can be:

• Put-away - Means you are receiving the goods and putting them into the Bin and
• Picking- Means you are issuing the goods

T-codes and Process

You can have purchase requisition or RFQ that you will process to create purchase order.But you easy understanding I am starting this process from creation of purchase order

1. ME21N- Create Purchase Order- Here we will use Material Master and Vendor Master to create purchase order. If there is release strategy applicable, make sure you release the PO before proceeding to next step

Key Points to taken care

We are going to make use of inbound deliveries for this process. System will only allow you to create inbound delivery on purchase orders if you confirmations mentioned in the purchase order. To create inbound delivery make sure you have confirmation control 0004- Inbound delivery or configured copy of 0004.

Confirmation Tab is available at purchase order item level. Confirmation Control key can mentioned in vendor master or in purchasing info records to populate as default at time of purchase order creation

• This enable you to use VL31N to create the inbound delivery document w.r.t approved purchase order

Notes- Info Record is optional, if you do not have info records system will still allow you to create purchase order.

2. Create Inbound Delivery-VL31N

Inbound delivery is used to provide information about goods receipt. This is not a goods receipt but this can notification from vendors about shipping of goods or intermediate stage before goods receipt is posted.

You can do goods receipt w.r.t. to inbound delivery without using WM.

Inbound delivery- This is confirmation document that enable business to capture the shipping stage or gate entry as soon material is shipped by the vendor or received at the store gate

Transfer order can be created using

• Using T-Code-LT0F
• Using VL06IP-Inbound Deliveries for Put-away. You can also schedule it as background job to create the transfer orders. Program Name-WS_MONITOR_INB_DEL_PICK
• Using Subsequent functions in VL31N/VL32N- can also create the transfer order (see picture below)

Once Transfer order is created, Next Step is to do confirm the transfer order

Note:- You can use LT21 to display Transfer order

3. Confirmation of Transfer Order  T-Code LT12 or using RFGUN

Press Enter to proceed further

Results

• - IM inventory is updated
• - WM Inventory get moved to storage bins from goods receipt interim storage type
• - Purchase order history and delivery document flows get updated

Display Document Flow in Delivery- VL33N

Goods Receipt Reversal Process in WM

Prerequisites

• - Inbound delivery creation
• - Transfer order is confirmed
• - Material Document is posted

Cancel the goods movement document for Delivery- VL09

• - Enter the delivery number and click on execute button (F8)

If everything is ok, above message will be displayed- System will open Delivery again and document flow and purchase order history will get updated

Note- Cancellation in VL09 for material document does not create transfer order for reversal

Results

• - Inventory from SAP IM get cleared as soon as reversal is posted
• - Purchase Order history updated
• - Delivery Document flow is updated

Return to Stock from Delivery T-code LT0G

• - Enter warehouse number
• - Enter Inbound delivery number and click on execute button (F8)

• - Click on button “Return to Stock”

This will return the stock from fixed bins to interim storage type for goods receipt and also create reverse transfer order

• - Click on “Log” Button to display transfer order created by LT0G

Results

• - Reverse Transfer order is created to clear the inventory from WM

Confirm Transfer Order-LT12

Click on save button to confirm the transfer order

Results

• - Stock will be moved  to WM Bin
• - Delivery document flow will be updated
• - Delivery can be deleted

I am sharing my recent experience with SAP Fiori. There are 200+ apps that have been delivered on SAP. SAP Fiori enable you to use your tablet, iphone or any Android phone to access SAP applications.

Purpose

Approve Purchase Orders, you can view pending purchase orders and approve them. If necessary, you can forward approvals to a different employee for further processing.

Key Features

• You can search for specific purchase orders.
• You can display details for each purchase order, for example, the line items with detailed information, such as account assignment and conditions.
• You can approve or reject purchase orders, and you can forward them to a colleague.

Prerequisites

1. Configuration of release strategy is done with Workflow
2. Fiori Add-On Components are installed on your system
3. You also need SAP Gateway to use add-on component as O data service
   

Configuration Requirement

SAP Fiori Inbox on SAP workflow tasks assigned to user in his SAP inbox. You can also check pending requests available in SWBP transaction.

SPRO-->Materials Management-->Purchasing-->Purchase Order-->Approve Purchase Order App

I used Standard Workflow Task-TS20000166

In this Customizing activity, you can specify the workflow tasks that are used for approving purchase orders in SAP ERP.  You must do this to enable the approval workflow in the Approve Purchase Orders app.

Note

• If you are using the user interface software component UIAPP002 from the add-on FIORI PURCHASEORDAPPR 1.0,  this Customizing activity is not relevant.

• If you have previously used the user interface software component UIAPP002, you have performed Customizing steps in the Gateway system under SAP NetWeaver -> Gateway Service Enablement -> Content -> Task Gateway Service -> Scenario Definition.  This Customizing is no longer relevant if you are now using the user interface software component UIX01EAP. However, you do not need to delete this Customizing.

Requirements

You are using the user interface software component UIX01EAP from the add-on FIORI ERP APPLICATIONS  X1.

Activities

To find the workflow tasks you need to enter in this Customizing activity, proceed as follows:

1. Start transaction SWETYPV.

2. Find a line to which the following applies:

• The ObjectType is BUS2012 (purchase order).

• The Event is RELEASESTEPCREATED.

• The checkbox Type linkage active is selected.

3. Copy the entry for Receiver Type in the same line to your clipboard.

4. Start the Workflow Builder (transaction SWDD).

5. Enter the content of the clipboard into the Workflow field and press ENTER. In the Navigation Area, you see a list of steps.

Approval Steps

1. Log on the website link using any browser or configure your Fiori App on your Android system

2. Enter Username and password

3. Scroll down to “Buyer” Section and Click “Approve Purchase Orders” logo

4. Select the Purchase Order number on Left side to look into details

You can also see the items details such as Price, Discount and any other information.

Now user have option to click on "Approve" Button or "Reject" Button or "Forward" button.

Approver can also maintains his comments while approving the purchase order and these comments get maintained in the purchase order header level text

Back-Text PO approval notes is maintained.