Transaction and Process Keys in MM

Hi BW Experts,
Can any one please tell me what are Transaction and Process Keys in MM.
What is the use of these keys and how it is implemented in BW.
Thanks in Advance.
Tony

Hi
Please find the below threads
Re: What are process KEYS in MM
https://www.sdn.sap.com/irj/sdn/advancedsearch?query=process%20keys&cat=sdn_all
Hope it helps
Thanks
Teja

Similar Messages

Transaction and Process or sub-Process Automation

I am undertaking a market survey of business process and in particular transaction or sub process automation in the SAP landscape. I am particularly interested in talking to SAP users who are operationally focused or people who are involved in business analysis or operations sustainment roles. The format of the interviews is one-on-one phone or face to face conversations lasting 30 minutes to 1 hour and will be your opportunity to tell me about methods and tools that you use to automate transactions and sub processes, why you do this and perhaps some of the gaps you see in the tools available. Participants in the survey will have the benefit of receiving summaries of the findings of the surveys as well as other research discoveries. If you are interested in participating then please contact me.

Hi
Please find the below threads
Re: What are process KEYS in MM
https://www.sdn.sap.com/irj/sdn/advancedsearch?query=process%20keys&cat=sdn_all
Hope it helps
Thanks
Teja

Movement Type and Process/Transaction Key

I have scoured SDN for a clear definition on this question but haven't found anything on this yet.
I need to know, in Inventory, what is the difference between a Movement Type and Process Keys.
Where can I see what Movement Types are associated with what Process/Transaction Keys.

I have scoured SDN for a clear definition on this question but haven't found anything on this yet.
I need to know, in Inventory, what is the difference between a Movement Type and Process Keys.
Where can I see what Movement Types are associated with what Process/Transaction Keys.

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

EBS external transactions – Interpretation algorithms and processing types

When assigning external transactions I am unclear about how best to use the Interpretation Algorithm and Processing type fields. Does anyone have some practical examples to help me understand how to use these tools?

In the global configuration for EBS, you map external transactions to internal transactions (posting rules) within a transaction type. You then assign each bank key and bank account combination to the transaction type that should be used for processing statements for that account. If you want different external transaction mappings for different account IDs, then you need to create different transaction types and assign each account to the relevant transaction type. Since the transaction types are assigned to the account numbers, you can have different transaction types for accounts with the same bank key.
Regards,
Shannon

I am trying to connect my iMac with my MacBook What is the command keys and process in doing so. Have firmwre in place.

I am trying to connect my iMac with my MacBook What is the command keys and process in doing so. Have firmwre in place.

Here's the Apple Support article on Target Mode http://support.apple.com/kb/HT1661

Customize approval process on transaction and receipt in Oracle AR

Dear all,
Is there anyone ever customize an approval function on AR transaction and AR receipt process? Can you share how you can achieve the customization, esp on the receipt process?
HY

Hi,
I feel there is one workaround for this issue, but evaluate this as per your requirement.
Enable Journal approval for Receivables Journal Source and periodically post the Journal entries of Receivables to General Ledger.
Ask the approver to approve the receipts in General Ledger. (Using drilldown functionality if required).
If there is any mistake the approver can always ask for reversal of Original receipt and direct the user to enter new one.
Only drawback is Sales Invoices should also be approved. These should be approved blindly.
Regards,
Sridhar

Idoc Message type and Process Cosde for CJ01 transaction

Hi,
What is the Idoc message type and inbound Process code for CJ01 transdaction?
Is there Any standard procedure to find out Idoc Mesage type and process codes for particular application?
Thanks.

Hi,
All the sending and receiving programs(transaction) start with BD. e.g. if you want to send the material you can use the BD10 transaction and IDOC is available for the same.
Go to se93 and search for BD* and look for the description.
Regards,
Nilesh.

How can we correct and process errorrecords in session and call transaction

hai all
how ca we correct and process error records in session and call transaction method . tell me with coding.
Edited by: swamy katta on May 14, 2008 10:25 AM
Edited by: swamy katta on May 14, 2008 10:26 AM
Edited by: swamy katta on May 14, 2008 10:27 AM

hi,
Check out the below sample code ...Here are the records are getting posting with call transaction method and a session is getting created with erroreneous records....
REPORT ztest_report
NO STANDARD PAGE HEADING
                        LINE-SIZE 255
                        MESSAGE-ID ZRASH.
*                 Internal Table Declarations                          *
*--Internal Table for Data Uploading.
DATA : BEGIN OF IT_FFCUST OCCURS 0,
         KUNNR(10),
         BUKRS(4),
         KTOKD(4),
         ANRED(15),
         NAME1(35),
         SORTL(10),
         STRAS(35),
         ORT01(35),
         PSTLZ(10),
         LAND1(3),
         SPRAS(2),
         AKONT(10),
       END OF IT_FFCUST.
*--Internal Table to Store Error Records.
DATA : BEGIN OF IT_ERRCUST OCCURS 0,
         KUNNR(10),
         EMSG(255),
       END OF IT_ERRCUST.
*--Internal Table to Store Successful Records.
DATA : BEGIN OF IT_SUCCUST OCCURS 0,
         KUNNR(10),
         SMSG(255),
       END OF IT_SUCCUST.
*--Internal Table for Storing the BDC data.
DATA : IT_CUSTBDC LIKE BDCDATA OCCURS 0 WITH HEADER LINE.
*--Internal Table for storing the messages.
DATA : IT_CUSTMSG LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
DATA : V_FLAG1(1) VALUE ' ',
"Flag used for opening session.
       V_TLINES LIKE SY-TABIX,
       "For storing total records processed.
       V_ELINES LIKE SY-TABIX,
       "For storing the no of error records.
       V_SLINES LIKE SY-TABIX.
       "For storing the no of success records.
*          Selection screen                                            *
SELECTION-SCREEN BEGIN OF BLOCK B1.
PARAMETERS : V_FNAME LIKE RLGRAP-FILENAME,
             V_SESNAM LIKE RLGRAP-FILENAME.
SELECTION-SCREEN END OF BLOCK B1.
*          Start-of-selection                                          *
START-OF-SELECTION.
*-- Form to upload flatfile data into the internal table.
PERFORM FORM_UPLOADFF.
*        TOP-OF-PAGE                                                   *
TOP-OF-PAGE.
WRITE:/ 'Details of the error and success records for the transaction'
ULINE.
SKIP.
*          End of Selection                                            *
END-OF-SELECTION.
*-- Form to Generate a BDC from the Uploaded Internal table
PERFORM FORM_BDCGENERATE.
*--To write the totals and the session name.
PERFORM FORM_WRITEOP.
*&      Form form_uploadff
*     Form to upload flatfile data into the internal table.
FORM FORM_UPLOADFF .
*--Variable to change the type of the parameter file name.
DATA : LV_FILE TYPE STRING.
LV_FILE = V_FNAME.
*--Function to upload the flat file to the internal table.
CALL FUNCTION 'GUI_UPLOAD'
    EXPORTING
      FILENAME                      = LV_FILE
*     FILETYPE                      = 'ASC'
      HAS_FIELD_SEPARATOR           = 'X'
*     HEADER_LENGTH                 = 0
*     READ_BY_LINE                  = 'X'
*     DAT_MODE                      = ' '
*   IMPORTING
*     FILELENGTH                    =
*     HEADER                        =
    TABLES
      DATA_TAB                      = IT_FFCUST
    EXCEPTIONS
      FILE_OPEN_ERROR               = 1
      FILE_READ_ERROR               = 2
      NO_BATCH                      = 3
      GUI_REFUSE_FILETRANSFER       = 4
      INVALID_TYPE                  = 5
      NO_AUTHORITY                  = 6
      UNKNOWN_ERROR                 = 7
      BAD_DATA_FORMAT               = 8
      HEADER_NOT_ALLOWED            = 9
      SEPARATOR_NOT_ALLOWED         = 10
      HEADER_TOO_LONG               = 11
      UNKNOWN_DP_ERROR              = 12
      ACCESS_DENIED                 = 13
      DP_OUT_OF_MEMORY              = 14
      DISK_FULL                     = 15
      DP_TIMEOUT                    = 16
      OTHERS                        = 17
IF SY-SUBRC = 0.
*--Deleting the headings from the internal table.
    DELETE IT_FFCUST INDEX 1.
*--Getting the total number of records uploaded.
    DESCRIBE TABLE IT_FFCUST LINES V_TLINES.
ENDIF.
ENDFORM.                    " form_uploadff
*&      Form Form_bdcgenerate
*     Form to Generate a BDC from the Uploaded Internal table
FORM FORM_BDCGENERATE .
*--Generating the BDC table for the fields of the internal table.
LOOP AT IT_FFCUST.
    PERFORM POPULATEBDC USING :
                                'X' 'SAPMF02D' '0105',
                                ' ' 'BDC_OKCODE' '/00' ,
                                ' ' 'RF02D-KUNNR' IT_FFCUST-KUNNR,
                                ' ' 'RF02D-BUKRS' IT_FFCUST-BUKRS,
                                ' ' 'RF02D-KTOKD' IT_FFCUST-KTOKD,
                                'X' 'SAPMF02D' '0110' ,
                                ' ' 'BDC_OKCODE' '/00',
                                ' ' 'KNA1-ANRED' IT_FFCUST-ANRED,
                                ' ' 'KNA1-NAME1' IT_FFCUST-NAME1,
                                ' ' 'KNA1-SORTL' IT_FFCUST-SORTL,
                                ' ' 'KNA1-STRAS' IT_FFCUST-STRAS,
                                ' ' 'KNA1-ORT01' IT_FFCUST-ORT01,
                                ' ' 'KNA1-PSTLZ' IT_FFCUST-PSTLZ,
                                ' ' 'KNA1-LAND1' IT_FFCUST-LAND1,
                                ' ' 'KNA1-SPRAS' IT_FFCUST-SPRAS,
                                'X' 'SAPMFO2D' '0120',
                                ' ' 'BDC_OKCODE' '/00',
                                'X' 'SAPMF02D' '0125',
                                ' ' 'BDC_OKCODE' '/00',
                                'X' 'SAPMF02D' '0130',
                                ' ' 'BDC_OKCODE' '=ENTR',
                                'X' 'SAPMF02D' '0340',
                                ' ' 'BDC_OKCODE' '=ENTR',
                                'X' 'SAPMF02D' '0360',
                                ' ' 'BDC_OKCODE' '=ENTR',
                                'X' 'SAPMF02D' '0210',
                                ' ' 'KNB1-AKONT' IT_FFCUST-AKONT,
                                ' ' 'BDC_OKCODE' '/00',
                                'X' 'SAPMF02D' '0215',
                                ' ' 'BDC_OKCODE' '/00',
                                'X' 'SAPMF02D' '0220',
                                ' ' 'BDC_OKCODE' '/00',
                                'X' 'SAPMF02D' '0230',
                                ' ' 'BDC_OKCODE' '=UPDA'.
*--Calling the transaction 'fd01'.
    CALL TRANSACTION 'FD01' USING IT_CUSTBDC MODE 'N' UPDATE 'S'
    MESSAGES INTO IT_CUSTMSG.
    IF SY-SUBRC <> 0.
*--Populating the error records internal table.
      IT_ERRCUST-KUNNR = IT_FFCUST-KUNNR.
      APPEND IT_ERRCUST.
      CLEAR IT_ERRCUST.
*--Opening a session if there is an error record.
      IF V_FLAG1 = ' '.
        PERFORM FORM_OPENSESSION.
        V_FLAG1 = 'X'.
      ENDIF.
*--Inserting the error records into already open session.
      IF V_FLAG1 = 'X'.
        PERFORM FORM_INSERT.
      ENDIF.
*--Populating the Success records internal table.
    ELSE.
      IT_SUCCUST-KUNNR = IT_FFCUST-KUNNR.
      APPEND IT_SUCCUST.
      CLEAR IT_SUCCUST.
    ENDIF.
*--Displaying the messages.
    IF NOT IT_CUSTMSG[] IS INITIAL.
      PERFORM FORM_FORMATMSG.
    ENDIF.
*--Clearing the message and bdc tables.
    CLEAR : IT_CUSTBDC[],IT_CUSTMSG[].
ENDLOOP.
*--Getting the total no of error records.
DESCRIBE TABLE IT_ERRCUST LINES V_ELINES.
*--Getting the total no of successful records.
DESCRIBE TABLE IT_SUCCUST LINES V_SLINES.
*--Closing the session only if it is open.
IF V_FLAG1 = 'X'.
    PERFORM FORM_CLOSESESS.
ENDIF.
ENDFORM.                    " Form_bdcgenerate
*&      Form populatebdc
*       FOrm to Populate the BDC table.
FORM POPULATEBDC USING    VALUE(P_0178)
                           VALUE(P_0179)
                           VALUE(P_0180).
IF P_0178 = 'X'.
    IT_CUSTBDC-PROGRAM = P_0179.
    IT_CUSTBDC-DYNPRO = P_0180.
    IT_CUSTBDC-DYNBEGIN = 'X'.
ELSE.
    IT_CUSTBDC-FNAM = P_0179.
    IT_CUSTBDC-FVAL = P_0180.
ENDIF.
APPEND IT_CUSTBDC.
CLEAR IT_CUSTBDC.
ENDFORM.                    " populatebdc
*&      Form FORM_OPENSESSION
*       Form to Open a session.
FORM FORM_OPENSESSION .
*--Variable to convert the given session name into reqd type.
DATA : LV_SESNAM(12).
LV_SESNAM = V_SESNAM.
*--Opening a session.
CALL FUNCTION 'BDC_OPEN_GROUP'
   EXPORTING
     CLIENT                    = SY-MANDT
     GROUP                     = LV_SESNAM
     HOLDDATE                  = '20040805'
     KEEP                      = 'X'
     USER                      = SY-UNAME
     PROG                      = SY-CPROG
* IMPORTING
*    QID                       =
   EXCEPTIONS
     CLIENT_INVALID            = 1
     DESTINATION_INVALID       = 2
     GROUP_INVALID             = 3
     GROUP_IS_LOCKED           = 4
     HOLDDATE_INVALID          = 5
     INTERNAL_ERROR            = 6
     QUEUE_ERROR               = 7
     RUNNING                   = 8
     SYSTEM_LOCK_ERROR         = 9
     USER_INVALID              = 10
     OTHERS                    = 11
IF SY-SUBRC <> 0.
    WRITE :/ 'Session not open'.
ENDIF.
ENDFORM.                    " FORM_OPENSESSION
*&      Form FORM_INSERT
*       fORM TO INSERT ERROR RECOED INTO A SESSION.
FORM FORM_INSERT .
*--Inserting the record into session.
CALL FUNCTION 'BDC_INSERT'
    EXPORTING
      TCODE                  = 'FD01'
*     POST_LOCAL             = NOVBLOCAL
*     PRINTING               = NOPRINT
*     SIMUBATCH              = ' '
*     CTUPARAMS              = ' '
    TABLES
      DYNPROTAB              = IT_CUSTBDC
    EXCEPTIONS
      INTERNAL_ERROR         = 1
      NOT_OPEN               = 2
      QUEUE_ERROR            = 3
      TCODE_INVALID          = 4
      PRINTING_INVALID       = 5
      POSTING_INVALID        = 6
      OTHERS                 = 7
IF SY-SUBRC <> 0.
    WRITE :/ 'Unable to insert the record'.
ENDIF.
ENDFORM.                    " FORM_INSERT
*&      Form FORM_CLOSESESS
*       Form to Close the Open Session.
FORM FORM_CLOSESESS .
CALL FUNCTION 'BDC_CLOSE_GROUP'
    EXCEPTIONS
      NOT_OPEN    = 1
      QUEUE_ERROR = 2
      OTHERS      = 3.
IF SY-SUBRC <> 0.
ENDIF.
ENDFORM.                    " FORM_CLOSESESS
*&      Form FORM_FORMATMSG
*       Form to format messages.
FORM FORM_FORMATMSG .
*--Var to store the formatted msg.
DATA : LV_MSG(255).
CALL FUNCTION 'FORMAT_MESSAGE'
    EXPORTING
      ID        = SY-MSGID
      LANG      = SY-LANGU
      NO        = SY-MSGNO
      V1        = SY-MSGV1
      V2        = SY-MSGV2
      V3        = SY-MSGV3
      V4        = SY-MSGV4
    IMPORTING
      MSG       = LV_MSG
    EXCEPTIONS
      NOT_FOUND = 1
      OTHERS    = 2.
IF SY-SUBRC = 0.
    WRITE :/ LV_MSG.
ENDIF.
ULINE.
ENDFORM.                    " FORM_FORMATMSG
*&      Form form_writeop
*       To write the totals and the session name.
FORM FORM_WRITEOP .
WRITE :/ 'Total Records Uploaded :',V_TLINES,
           / 'No of Error Records :',V_ELINES,
           / 'No of Success Records :',V_SLINES,
           / 'Name of the Session :',V_SESNAM.
ULINE.
ENDFORM.                    " form_writeop
* if routeindicator is initial.
*   LOOP AT IT_YMMEE00090.
*      LV_LENGTH = STRLEN( IT_YMMEE00090-CHANGETYPE ).
*      IF SY-TABIX = '1'.
*        IF IT_YMMEE00090-CHANGETYPE = 'B' AND LV_LENGTH = 1.
*          ROUTEINDICATOR = 'S'.
*        ELSEIF IT_YMMEE00090-CHANGETYPE = 'R' AND LV_LENGTH = 1.
*          ROUTEINDICATOR = 'S'.
*        ELSEIF IT_YMMEE00090-CHANGETYPE = 'S' AND LV_LENGTH = 1.
*          ROUTEINDICATOR = 'S'.
*        ELSEIF IT_YMMEE00090-CHANGETYPE CA 'BRSCD' AND LV_LENGTH GT 1
*                                          AND LV_LENGTH LE 5.
*          ROUTEINDICATOR = 'S'.
*        ENDIF.
*      ELSE.
*        IF IT_YMMEE00090-CHANGETYPE = 'B' AND LV_LENGTH = 1 AND
*                                         ROUTEINDICATOR = 'S'.
*          ROUTEINDICATOR = 'S'.
*        ELSEIF IT_YMMEE00090-CHANGETYPE = 'R' AND LV_LENGTH = 1 AND
*                                         ROUTEINDICATOR = 'S'.
*          ROUTEINDICATOR = 'S'.
*        ELSEIF IT_YMMEE00090-CHANGETYPE = 'S' AND LV_LENGTH = 1 AND
*                                         ROUTEINDICATOR = 'S'.
*          ROUTEINDICATOR = 'S'.
*        ELSEIF IT_YMMEE00090-CHANGETYPE CA 'BRSCD' AND LV_LENGTH GT 1
*                  AND LV_LENGTH LE 5 AND ROUTEINDICATOR = 'S'.
*          ROUTEINDICATOR = 'S'.
*        ENDIF.
*      ENDIF.
* ENDLOOP.
* endif.

Trap back button processing and exit transaction and re-enter program.

Hi
I wonder if one of you guru's can help me. We seem to be getting loads of short dumps and I have been assigned the task of looking into it. Basically we have a program that the user runs (transaction FBL5N - Program is RFITEMAR).
When the user executes the program he/she will be presented with a list of customer line item display they then select the items they want to view and press the display icon that gives a more detailed view.
When they press the back button it goes back to the list and they are able to select another item and repeat the above process.
My task is to trap the back button from the deatail screen (the last screen) and after trapping the back button I need to completely exit out of the transaction and then go back in at the point that they were at prior to going into the detailed screen.
This is required as we think everytime the user displays the detail screen the system is grabbing memomry and not relinquishing it.
Many thanks in advance .
Raj
Disagramatically
=============
Currently
=======
screen 1 (selection screen) --> execute
                  screen 2 --> (select item & press detail icon)
                            screen 3 (detail info) press back
                  screen 2 --> (select item & press detail icon)
                            screen 3 (detail info) press back
                  screen 2 --> (select item & press detail icon)
                            screen 3 (detail info) press back
                  screen 2 --> (select item & press detail icon)
                            screen 3 (detail info) press back
What I require
============
screen 1 (selection screen) --> execute
                  screen 2 --> (select item & press detail icon)
                            screen 3 (detail info) press back
                  exit transaction and then go to
                  screen 2 --> (select item & press detail icon)
                            screen 3 (detail info) press back
                  exit transaction and then go to
                  screen 2 --> (select item & press detail icon)
                            screen 3 (detail info) press back
                  exit transaction and then go to
                  screen 2 --> (select item & press detail icon)
                            screen 3 (detail info) press back

trap the back button
its not at all clear...
ur req is from screen 3 ->display document    then on back button
screen 2 the list display...
The report acts in the same way ....

Transaction code to find Process message and Process Instruction

Hi
I am new to PP module
Where do i find (In which Transaction) the list of
a) Process Message Category
b) Process message
c) Process Instruction Category
in SAP ERP system??
Regards
Sweety

Hi
Thank u all for responding
Still I was not able to find certain Process Messages like YQ_AIR, YQ_RPM, YQ_TEMP, YQ_CONS, YQ_PHCO, YQ_PHCO2.
and Process Instructions like
YQ_AIR, YQ_ENDPI,YQ_HEAD, YQ_INSTR, YQ_LAY, YQ_MATLI, YQ_PROD, YQ_PTEXT,YQ_RPM, YQ_TEMP, YQ_CON1, YQ_CON2..
do I need to do some (Basis) configuration to get these?? or the above mentioned Process Messages and Process Instructions are not pre defined??
Regards
Sweety

"created by" in SAP transactions and CE BPM

Dear all,
In most of the transaction e.g. create Purchase Order - "created by" is field available in BAPI. In case of Investment approval processes "created by" is popultaed by the ID assigned to logical destination "BASIC" authorisation.
How is this implemented, any guidline?
If EP user creates transaction on SAP, how do we get report / analysis of EP user wise transaction and noty user specified in BASIS authorisation?
how does licencing affects if we use BASIC authorisation?
Ajay

Hi
How is this implemented, any guidline : CreatedBy,CreationDate ,Time.. these are some standard Business Attribute which is by default get assigned to BAPI ,EJB. other than our normal field which actually a key attribute for that implementation. We do not need to give any value/implementation for these attribute it take the data automatically from system .
Hope it helps .
Best Regards
Satish Kumr

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 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

Transaction and Process Keys in MM

Similar Messages

Maybe you are looking for