Processing Key In MRP

hi,
I wanted some clarification regarding the Processing key under MRP Control Parameters in MD01
The following values are found linked to this field.
NETCH
NETPL
NEUPL
Could someone explain how exactly these keys work.and what is their significance.
Regards
Lyroj

Hi,
NEUPL: System plans all the materials that are contained in the planning file
NETCH: In net change planning only those materials are planned for which the net change planning indicator in the planning file has been set as a planning file entry. The system usually sets the indicator automatically as soon as a change is made to the material that is relevant to MRP.
NETPL: The system only plans materials that have undergone a change that is relevant to the planning run within the period which you defined as the planning horizon. The system sets the net change planning horizon indicator automatically for these materials .
Regards,
satyajit

Similar Messages

MRP run - Processing key

Hi all,
In the screen of MD02, Processing key NETCH was coming defaultly,
But when I run MRPtwo-three times using NETPL, so same bocame default.
Now I want to make it NETCH but system is not allowing me.
How can I change that?
Thaks

Dear Bharat,
In T code MD02 Goto Settings ---> Delete and then again assign the parameters which you want and then click on top menu settings --
-->save.
come out of the screen and then agian check T code MD02.
Regards
Mangalraj.S

MRP Processing Key defaulted to NETPL

Hi,
We have a requirement wherein we need the Processing Key defaulted to "NETPL" mode whenever we are running MD01 or MD02 transaction.
Currently, it is defaulted to NETCH.
Do we have a SAP note or BADI in place which can facilitate this feature?
Appreciate your help here.
regards,
Rishi.N.Khanduri

Hello ADM,
Your requirement fulfill through variant
Please go to SM38
enter Program RMMPS000 select variant, Execute
create new variant “xxx”
Maintain the filed as per your requirement
Ex: Processing key, Planning mode, scheduling etc,
And Save
Go to SM36:
Create batch job and assign this Variant to this batch job
Schedule your Batch job and run as per your requirement
I hope this information helpful to you
Regards
Umesh Mali

Inventory management process key values plz

Hi gurus,
can anyone help me with the process key values
in my update rules i have this for issues
process keys= 100,101,104,105,106,110
and for receipts 000,001,004,005,006,010
what do they mean i am using the standard update rules
its very urgent becoz i am getting the stock values wrong
thanks and regards
neelu

hi Neel,
check oss note 352344 - Process key + reversals in Inventory Management ?
Symptom
This note is a consulting note and describes the use of the process key (0PROCESSKEY) in Inventory Management (MSEG). It focusses on the way the system deals with reversed transactions for DataSources 2lis_40_s279 and 2lis_03_bf.
To be able to use theses DataSources, you ABSOLUTELY MUST activate the transaction key generation (process key, PROCESSKEY) using Transaction MCB_ (from the OLTP IMG for BW: SBIW) (standard, retail or consumption goods).
The following transaction keys are available
(PROCESSKEY/Appl. Component/Description):
000/MM        Misc. receipts
001/MM        Goods receipt / vendor
004/MM        Article transfer posting receipt
005/MM        Stock correction inventory +
006/MM        Stock correction other +
007/IS-R      Receipt value-only article (single article
              posting)
010/MM        Receipt from stock transfer
002/IS-R      Merchandise clearing receipt
003/IS-R      GR from DC
100/MM        Misc. issues
101/MM        Returns / Vendor
104/MM        Article transfer posting issue
105/MM        Stock correction inventory -
106/MM        Stock correction other -
107/IS-R      Issue value-only article (single article
              posting)
110/MM        Issue from stock transfer
102/IS-R      Merchandise clearing issue
103/IS-R      GI from DC
450/IS-R      Generic Article (not relevant)
Remark: Transaction keys 002/003, 102/103 break down the core keys 010/110 in more detail with respect to retail processes. They are only available in an R/3 Retail.
As you can see in the overview, the transaction keys can be divided according to receipts and issues in Inventory Management. Furthermore, the transaction keys are displayed according to reversed and regular transactions.
A regular receipt has a debit/credit indicator "S" (SHKZG, 0DCINDIC), whereas a regular issue has a debit/credit indicator "H".
For reverse transactions the opposite is true.
Transaction                            D/C ind.   D/C ind.
                                        S          H
RECEIPTS
0 Misc. receipts                        regular    reversed
1 Goods receipt / vendor               regular    reversed
2 Merchandise clearing receipt        regular    reversed
3 GR from DC                            regular    reversed
4 Article transfer posting receipt    regular    reversed
5 Stock correction inventory +        regular    reversed
6 Stock correction other +            regular    reversed
7 Receipt value-only article          regular    reversed
10 Receipt from stock transfer        regular    reversed
ISSUES
100 Misc. issues                       reversed   regular
101 Returns / vendor                   reversed   regular
102 Merchandise clearing issue        reversed   regular
103 GI from DC                         reversed   regular
104 Article transfer posting issue    reversed   regular
105 Stock correction inventory -      reversed   regular
106 Stock correction other -          reversed   regular
107 Issue value-only article          reversed   regular
110 Issue from stock transfer         reversed   regular
Note: You can also recognize a reversal for DataSource 2lis_03_bf by means of the entry 0STORNO = ´X´. The fields that are marked with X in the table are then transferred with negative +/- sign. This was not the case with DataSource 2LIS_40_S279!!! In the case of DataSource 2LIS_40_S279 more logic was required in the BW update rules to make sure that key figures were updated correctly.
Example:
In the delivered InfoCubes 0CP_IC_C1 (CP) and 0RT_C01 (Retail), for example in key "Stock correction +", transaction keys 5 and 6 were grouped together. Furthermore, distinction is to be made between the different stock types. Depending on which stock types you want to distinguish between in different key figures, you must use a corresponding condition (IF statement) in the update rules in the BW.
Example (pseudo source code):
Updating Routine "stock adjustment +" for 2lis_02_bfIF ( STOCKCAT is initial ) AND         "Evaluated stocks ( PROCESSKEY = 5 OR PROCESSKEY = 6 )._ RESULT = TRANS_AMOUNT. RETURNCODE = 0.    "Updating Key figureELSE. RETURNCODE = 4.    "No Updating of KeyfigureENDIF.
The pseudo source code for 2LIS_40_S279 read as follows:
Updating Routine "stock adjustment +" for 2lis_40_s279IF ( STOCKCAT is initial ) AND         "Evaluated stocks ( PROCESSKEY = 5 OR PROCESSKEY = 6 ).    IF DCINDIC = 'S'.      RESULT = TRANS_AMOUNT.    "regular    ELSE.      RESULT = -1 * TRANS_AMOUNT.    ENDIF.    RETURNCODE = 0.    "Updating Key figureELSE.     RETURNCODE = 4.    "No Updating of KeyfigureENDIF.
Here, the debit/credit indicator must be checked in accordance with the table above. Transactions 5 and 6 are receipts in Inventory Management. As the debit/credit indicator is set to "S", it is a regular transaction whose value(TRANS_AMOUNT) is assigned to the key figure. In the other case (debit/credit indicator = "H") it is a reversal, that is, the transaction should reverse a transaction that has already been updated. For this, the value is multiplied by -1 so that a corresponding decrease/reduction of this key figure is achieved during the update of the key figure in the InfoCube.
This logic is no longer required for the 2LIS_03_BF (see first pseudo source code), because the reversed quantity and values are automatically provided as negative with the help of the 0STORNO field.
Using this DataSource 2LIS_03_BF, it is for example possible to create a key figure such as "Reversed receipts", which is not a part of the Business Content delivered. The following pseudo source code of an update routine makes this clear:
Update routine "Reversed receipts"
IF ( PROCESSKEY = 1 ) AND   (STORNO = ´X` ) "Reverse     RESULT = -1 * TRANS_AMOUNT.     RETURNCODE = 0.ELSE.     RETURNCODE = 4.      "no update of key figure!ENDIF.
Note: For DataSource 2LIS_40_S279 the pseudo source code read as follows:
Update routine "Reversed receipts"
for 2LIS_40_S279IF ( PROCESSKEY = 1 ) AND   ( DCINDIC = H ) "Reverse     RESULT = TRANS_AMOUNT.     RETURNCODE = 0.ELSE.   RETURNCODE = 4.      "no update of key figure!ENDIF.
To be able to understand the overall scheme more comprehensively, you should have a look at the update rules of the Standard Business Content for retail or consumption goods (for example InfoCubes 0RT_C01 or 0CP_IC_C1).

Process key issue in MM

Hi All,
I am working on 0PUR_C01 cube and theDS is 2lis_02_itm.i am facing a issue with the process key ,only process keys 2 and 3 are coming into the BI system even though process key 1 and others are also there in the source.
i have maintained the BF 11 flag and industry sector in mcb_.
please suggest.
Thanks
Sri

Hi, i'm having the same problem. Can you give me some guidance in how you solved the problem?
Thank you.
GG

Regarding Process Key

Hi all:
Friends I have struck up with my work due to Process key.
I need ur input for the following doubts.
1.What is process key?why we go for this?
2.What is the use of process key values like 1,2,21,22 ?..
Waiting for your reply....
Thanks in advance...
Rgds,
M.surendhar

Hi Surendhar
Please refer to following thread for Inventory process keys
Re: Customer Group in 2LIS_12_VCITM incorrect
Please refer to following thread for process keys used in MM
Re: What are process KEYS in MM
Hope this helps
Regards
Pradip

Process keys maintenance for Inventory data

Hi,
Can any one suggets the Procedure for to maintain the Process keys at the time of extracting Inventory data from Ecc6.0 to BI 7.0.
Thanks,
Chandra G

Hi Reddy,
first of all thanks for your quik Response.
BI consultant need to maintain the process key(transaction keys) or MM consultant. when i see that path, already some transaction keys are maintaining for MM there like
aplication component          application   operat    Description
MM                                      02                   1          Purchase order/vendor
MM                                      02                   2         Goods Receipt
MM                                      02                   3         Invoice/Vendor
is we need to do any other New Entries or Settings
Regards,
chandra G

Process Keys in MM

Hello,
can someone please explaint the concept of process keys in MM. We are implementing Purchasing in BW and I would lke know about Process Keys.
If you can point me to some documentation, that would be good.
Thanks
John

Hi John,
take a look to the OSS Note 353042 'Howto: Activate transaction key (PROCESSKEY)' and linked notes...and, however, refer to the transaction MCB0.
Hope it helps.
Bye,
Roberto

Enabling process keys on R/3 side

Hi All,
I have done an enhancement for 2lis_02_itm with few fields.
I have successfully completed this work and i can see the records in RSA3.
Now the client is asking that during testing they found that the process keys are not enabled in R/3 side.They told me to enable process keys.
Can any one please tell me how to do this.
I think we can do via BF11 Tcode but which settings I have to do I am not sure about it.
And please explain me about process keys.
This is very very urgent.
I would appreciate the earliest responce.
Thanks
S VR

Hi,
You need to make 2 settings in R/3 before filling the setuptable.
1) Industory sector selection
2) MAking a Tick mark for BW by using Tcode Bf11.
<b>Also Check OSS Note 353042 - Howto: Activate transaction key (PROCESSKEY)</b>
https://websmp104.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=353042&_NLANG=E
Symptom
Fields BWGEO, BWGEOO, BWGVP, BWGVO, BWNETWR, BWMNG, etc. of DataSources 2LIS_02_SCL, 2LIS_02_ITM, 2LIS_03_BF, 2LIS_03_UM, 2LIS_40_REVAL are not filled.
This may lead to the following:
The system does not perform any update into an InfoCube (for example: 0RT_C*, 0PUR_C01, 0CP_PURC1 and so on), even though data arrives in BW.
This occurs with the following InfoSources:
2LIS_02_SCL, 2LIS_02_ITM
2LIS_03_BF, 2LIS_03_UM
2LIS_40_REVAL
With some restriction, this symptom also occurs with the following InfoSources if they are used in connection with retail or consumer products. (InfoCube: 0RT_* or 0CP_* ).
2LIS_11_VAITM, 2LIS_12_VCITM, 2LIS_13_VDITM
Other terms
0PROCESSKEY, PROCESSKEY, 0RT_C01, 0RT_C02, 0RT_C03, 0RT_C04, BWBRTWR, BWGEO, BWGEOO, BWGVP, BWGVO, BWNETWR, BWMNG
Reason and Prerequisites
The process key (0PROCESSKEY and 0BWAPPLNM) of the InfoSources has not been filled. As a result, no key figures are updated because of the update routine of the participating InfoCube and along with it no records are inserted into the InfoCube. In each update routine, the system checks the content of the PROCESSKEY. If this field has no contents, then no data is written into the InfoCube because of the IF condition in the update rules.
Solution
So that you can work in the above mentioned InfoSources, you MUST activate the determination of the process key. This is done with the help of Transaction MCB_ which you can find in the OLTP IMG for BW (Transaction SBIW) in your attached R/3 source system.
Here you can choose your industry sector. 'Standard' and 'Consumer products' are for R/3 standard customers, whereas 'Retail' is intended for customers with R/3 Retail only.
You can display the characteristics of the process key (R/3 field BWVORG, BW field 0PROCESSKEY) by using Transaction MCB0.
If you have already set up historical data (for example for testing purposes) by using the setup transactions (Statistical Setup Programs) (for example: Purchasing: Tx OLI3BW, material movements: OLI1BW) into the provided setup tables (for example: MC02M_0SCLSETUP, MC03BF0SETUP), you unfortunately have to delete this data (Tx LBWG). After you have chosen the industry sector by using MCB_, perform the setup again, so that the system fills a valid transaction key for each data record generated. Then load this data into your connected BW by using 'Full update' or 'Initialization of the delta process'. Check, whether the system updates data into the involved InfoCubes now.
If all this is not successful, please see Note 315880, and set the application indicator 'BW' to active using Transaction 'BF11'.
Related notes:
157317 --> You MUST make sure that this note is relevant for you.
352344 -> Process key + reversals in Inventory Management
(Consulting note).
Bye
Dinesh

Why do we use process keys

Dear all,
Can any one tell me y we use process keys....in inventory........can anyone please tell me the importance of process keys... y do we use them in the update rules.
what is the significance of process keys
Regards
venu

Dear,
For this we need to understand how Business Contents/extractors are designed.
Well, based on applications there are different methods followed by SAP to differentiate different Business Events in Logistics Applications.
Say for example, for Logistics applications Process Keys are used to differentiate between different Business Events.
In Financials, we use 'Value Type' to differentiate whether the data is a planned data or a Actual data or budgeted or a commitment or forecast etc.
Since, logistics applications are Business Events oriented, documents are differentiated using Process Keys.
Thanks

Process Key in 2LIS_03_UM

Dear Friends,
Please explain me what is Process Key in 2LIS_03_UM Datasource, because we want to define our own Key figure in BW Update rules, s there we need to key some process key,so I need what is this Process key and where we can get it in ECC.
Eg:
IF ( COMM_STRUCTURE-processkey EQ '150'
    OR COMM_STRUCTURE-processkey EQ '151'
    OR COMM_STRUCTURE-processkey EQ '152' )
    AND COMM_STRUCTURE-bwapplnm EQ 'MM'
    AND COMM_STRUCTURE-AC_DOC_TYP EQ 'PR'
    AND COMM_STRUCTURE-cppvlc <> 0.
Thanks
Ganga

Hi Ganga,
I am not sure of the new key figure you are going to add in the update rules for 2lIS_03_UM but you may need to add this key figure to your Cube first which should be a non-cumuative and then only you can write any update routines for this new key figure. The following are the process keys we use for Revaluations
The following are for Receipts
050    "Other revaluation +
051    "Revaluation/ price change +
052    "Revaluation/inv. verif. +
These are for Issues
150 "Other revaluation -
151   "Revaluation/price change -
152   "Revaluation/ invoice verif.-
You may also need to mention the Zmovement types in these routines but I am not sure how you are going to get the correct values without the consideration of 0MOVE_TYPE in your routines.
Hope it helps...

Use of Process key in 2lis_12_vcitm

Hello friends,
Can some one help me in explaining why do we use process key(BWVORG) in the extractor 2lis_12_vcitm specifically?
Thanks
Srini...

Hi,
Look @ this thread... clearly explained by ahp
What are process KEYS in MM
Thanks

What is maintaining process keys in mm extraction

hi friends,
what is maintaining process keys in mm extraction
Thanking u
suneel.

Hi Suneel,
The process keys basically represent the type of transaction which has happened in the source system.
If you notice the update rules for the Purchasing cubes like 0PUR_C01, etc. You will see some routines like this:
IF COMM_STRUCTURE-PROCESSKEY = `001`.
              RESULT = COMM_STRUCTURE-TRANS_AMOUNT.
           ELSE.
              CLEAR RESULT. no update of key-figure
     ENDIF.
<b>This means that if the process key determines which KF should be populated for the same in the Cube.</b>
Some of the common process keys for Purchasing are:
Event MA (purchase order) and purchase order category 1 yield process key 001.
Event MA (purchase order) and purchase order category 2 yield process key 011.
Event MA (purchase order) and purchase order category 3 yield process key 021.
Event MB (goods receipt) and purchase order category 1 yield process key 002.
Event MB (goods receipt) and purchase order category 2 yield process key 012.
Event MB (goods receipt) and purchase order category 3 yield process key 022.
Event MC (invoice receipt) and purchase order category 1 yield process key 003.
Event MC (invoice receipt) and purchase order category 3 yield process key 023.
Event MD (scheduling agreement) and purchase order category 1 yield process key 004.
Event MD (scheduling agreement) and purchase order category 2 yield process key 014.
Event MD (scheduling agreement) and purchase order category 3 yield process key 024.
Event ME (contracts) and purchase order category 1 yield process key 008.
Event ME (contracts) and purchase order category 2 yield process key 028.
Event ME (contracts) and purchase order category 3 yield process key 028.
You can find more information if you search across the forum.
Thanks,
Amol

Process Key

Can any one please tell me the functionality of process keys and how to use it in inventory management.
Thanks ..

Hi Akash
check oss note 352344 - Process key + reversals in Inventory Management ?
Symptom
This note is a consulting note and describes the use of the process key (0PROCESSKEY) in Inventory Management (MSEG). It focusses on the way the system deals with reversed transactions for DataSources 2lis_40_s279 and 2lis_03_bf.
To be able to use theses DataSources, you ABSOLUTELY MUST activate the transaction key generation (process key, PROCESSKEY) using Transaction MCB_ (from the OLTP IMG for BW: SBIW) (standard, retail or consumption goods).
The following transaction keys are available
(PROCESSKEY/Appl. Component/Description):
000/MM Misc. receipts
001/MM Goods receipt / vendor
004/MM Article transfer posting receipt
005/MM Stock correction inventory +
006/MM Stock correction other +
007/IS-R Receipt value-only article (single article
posting)
010/MM Receipt from stock transfer
002/IS-R Merchandise clearing receipt
003/IS-R GR from DC
100/MM Misc. issues
101/MM Returns / Vendor
104/MM Article transfer posting issue
105/MM Stock correction inventory -
106/MM Stock correction other -
107/IS-R Issue value-only article (single article
posting)
110/MM Issue from stock transfer
102/IS-R Merchandise clearing issue
103/IS-R GI from DC
450/IS-R Generic Article (not relevant)
Remark: Transaction keys 002/003, 102/103 break down the core keys 010/110 in more detail with respect to retail processes. They are only available in an R/3 Retail.
As you can see in the overview, the transaction keys can be divided according to receipts and issues in Inventory Management. Furthermore, the transaction keys are displayed according to reversed and regular transactions.
A regular receipt has a debit/credit indicator "S" (SHKZG, 0DCINDIC), whereas a regular issue has a debit/credit indicator "H".
For reverse transactions the opposite is true.
Transaction D/C ind. D/C ind.
S H
RECEIPTS
0 Misc. receipts regular reversed
1 Goods receipt / vendor regular reversed
2 Merchandise clearing receipt regular reversed
3 GR from DC regular reversed
4 Article transfer posting receipt regular reversed
5 Stock correction inventory + regular reversed
6 Stock correction other + regular reversed
7 Receipt value-only article regular reversed
10 Receipt from stock transfer regular reversed
ISSUES
100 Misc. issues reversed regular
101 Returns / vendor reversed regular
102 Merchandise clearing issue reversed regular
103 GI from DC reversed regular
104 Article transfer posting issue reversed regular
105 Stock correction inventory - reversed regular
106 Stock correction other - reversed regular
107 Issue value-only article reversed regular
110 Issue from stock transfer reversed regular
Note: You can also recognize a reversal for DataSource 2lis_03_bf by means of the entry 0STORNO = ´X´. The fields that are marked with X in the table are then transferred with negative +/- sign. This was not the case with DataSource 2LIS_40_S279!!! In the case of DataSource 2LIS_40_S279 more logic was required in the BW update rules to make sure that key figures were updated correctly.
Example:
In the delivered InfoCubes 0CP_IC_C1 (CP) and 0RT_C01 (Retail), for example in key "Stock correction +", transaction keys 5 and 6 were grouped together. Furthermore, distinction is to be made between the different stock types. Depending on which stock types you want to distinguish between in different key figures, you must use a corresponding condition (IF statement) in the update rules in the BW.
Example (pseudo source code):
Updating Routine "stock adjustment +" for 2lis_02_bfIF ( STOCKCAT is initial ) AND "Evaluated stocks ( PROCESSKEY = 5 OR PROCESSKEY = 6 )._ RESULT = TRANS_AMOUNT. RETURNCODE = 0. "Updating Key figureELSE. RETURNCODE = 4. "No Updating of KeyfigureENDIF.
The pseudo source code for 2LIS_40_S279 read as follows:
Updating Routine "stock adjustment +" for 2lis_40_s279IF ( STOCKCAT is initial ) AND "Evaluated stocks ( PROCESSKEY = 5 OR PROCESSKEY = 6 ). IF DCINDIC = 'S'. RESULT = TRANS_AMOUNT. "regular ELSE. RESULT = -1 * TRANS_AMOUNT. ENDIF. RETURNCODE = 0. "Updating Key figureELSE. RETURNCODE = 4. "No Updating of KeyfigureENDIF.
Here, the debit/credit indicator must be checked in accordance with the table above. Transactions 5 and 6 are receipts in Inventory Management. As the debit/credit indicator is set to "S", it is a regular transaction whose value(TRANS_AMOUNT) is assigned to the key figure. In the other case (debit/credit indicator = "H") it is a reversal, that is, the transaction should reverse a transaction that has already been updated. For this, the value is multiplied by -1 so that a corresponding decrease/reduction of this key figure is achieved during the update of the key figure in the InfoCube.
This logic is no longer required for the 2LIS_03_BF (see first pseudo source code), because the reversed quantity and values are automatically provided as negative with the help of the 0STORNO field.
Using this DataSource 2LIS_03_BF, it is for example possible to create a key figure such as "Reversed receipts", which is not a part of the Business Content delivered. The following pseudo source code of an update routine makes this clear:
Update routine "Reversed receipts"
IF ( PROCESSKEY = 1 ) AND (STORNO = ´X` ) "Reverse RESULT = -1 * TRANS_AMOUNT. RETURNCODE = 0.ELSE. RETURNCODE = 4. "no update of key figure!ENDIF.
Note: For DataSource 2LIS_40_S279 the pseudo source code read as follows:
Update routine "Reversed receipts"
for 2LIS_40_S279IF ( PROCESSKEY = 1 ) AND ( DCINDIC = H ) "Reverse RESULT = TRANS_AMOUNT. RETURNCODE = 0.ELSE. RETURNCODE = 4. "no update of key figure!ENDIF.
To be able to understand the overall scheme more comprehensively, you should have a look at the update rules of the Standard Business Content for retail or consumption goods (for example InfoCubes 0RT_C01 or 0CP_IC_C1).
Thanks=Points in SDN
SANJEEV KUMAR HAMSALA

Relation between Inventory Process keys and movement types

Dear All,
Is there any way to find the relation between Inventory process keys (which is in SBIW-> Settings for Application specific data sources(PI) -->Logistics -->Settings for IBU Retail / CP --> Transaction key maintenance for SAP BW) and movement types .
Thanks in advance...
Regards,
Raju

Hi,
Please read the note below.
Note 353042 - Howto: Activate transaction key (PROCESSKEY)
It has something for you ....
The process key (0PROCESSKEY and 0BWAPPLNM) of the InfoSources has not been filled. As a result, no key figures are updated because of the update routine of the participating InfoCube and along with it no records are inserted into the InfoCube. In each update routine, the system checks the content of the PROCESSKEY. If this field has no contents, then no data is written into the InfoCube because of the IF condition in the update rules.
Solution
So that you can work in the above mentioned InfoSources, you MUST activate the determination of the process key. This is done with the help of Transaction MCB_ which you can find in the OLTP IMG for BW (Transaction SBIW) in your attached R/3 source system.
Here you can choose your industry sector. 'Standard' and 'Consumer products' are for R/3 standard customers, whereas 'Retail' is intended for customers with R/3 Retail only.
You can display the characteristics of the process key (R/3 field BWVORG, BW field 0PROCESSKEY) by using Transaction MCB0.
If you have already set up historical data (for example for testing purposes) by using the setup transactions (Statistical Setup Programs) (for example: Purchasing: Tx OLI3BW, material movements: OLI1BW) into the provided setup tables (for example: MC02M_0SCLSETUP, MC03BF0SETUP), you unfortunately have to delete this data (Tx LBWG). After you have chosen the industry sector by using MCB_, perform the setup again, so that the system fills a valid transaction key for each data record generated. Then load this data into your connected BW by using 'Full update' or 'Initialization of the delta process'. Check, whether the system updates data into the involved InfoCubes now.
If all this is not successful, please see Note 315880, and set the application indicator 'BW' to active using Transaction 'BF11'.
Hope this helps.
Raj

Processing Key In MRP

Similar Messages

Maybe you are looking for