What are process KEYS in MM

[Former Member]

COuld someone please explain what process keys are and what is thier significance on MM extractors....what i am looking for is an exact definition of process keys...

Thank you

[edwin_harpino]

hi Southie,

process key is used to interpret document information from r/3 to bw.

The extractors presented here represent, in principle, structures that collect document-specific information from the logistics application Purchasing and transfer it to the SAP BW.

Many key figures are yielded from the application. These must be transferred to the SAP BW with the help of the extractors. SAP ensures that document information is interpreted in advance with the help of a 'process key' so that key figures, which describe and measure the particular processes, can be more easily derived for customers.

how to

to activate : transaction Transaction MCB_ in r/3

sample in purchasing

Here is a list of the values that process key - BWVORG can assume, according with the purchasing item type, processed document and purchasing order type:

1 - For non return items:

a) Document type: Purchasing order

- Normal purchasing order - BWVORG = 001

- Stock transport order - BWVORG = 011

- Cross company order - BWVORG = 021

b) Document type: Goods receipt

- Normal purchasing order - BWVORG = 002

- Stock transport order - BWVORG = 012

- Cross company order - BWVORG = 022

c) Document type: Invoice receipt

- Normal purchasing order - BWVORG = 003

- Stock transport order - BWVORG = 013

- Cross company order - BWVORG = 023

d) Document type: Scheduling agreement

- Normal scheduling agreement - BWVORG = 004

- Stock transport agreement - BWVORG = 014

- Cross company agreement - BWVORG = 024

e) Document type: Contract

- Normal contract - BWVORG = 008

- Cross company contract - BWVORG = 028

f) Document type: Request of quotation

- Request of quotation - BWVORG = 009

- Quotation - BWVORG = 040

2 - For return items:

a) Document type: Purchasing order

- Normal purchasing order - BWVORG = 005

- Stock transport order - BWVORG = 015

- Cross company order - BWVORG = 025

b) Document type: Goods receipt

- Normal purchasing order - BWVORG = 006

- Stock transport order - BWVORG = 016

- Cross company order - BWVORG = 026

c) Document type: Invoice receipt

- Normal purchasing order - BWVORG = 007

- Stock transport order - BWVORG = 017

- Cross company order - BWVORG = 027

d) Document type: Scheduling agreement

- Normal scheduling agreement - BWVORG = 041

- Stock transport agreement - BWVORG = 051

- Cross company agreement - BWVORG = 061

[edwin_harpino]

hi Southie,

oss note 353042-Howto: Activate transaction key (PROCESSKEY) may also useful.

[Former Member]

Hi

I need some help regarding the MM - PO implementation in BW..

Is there is any possibliy so that i can see the vendor down payment and the other progreesive payments made to vendor.

we are using 2LIS_2_SCL and ACC for starters..

The requirement is bring the PO "DOWNPAYMENT" data into BW .

We get all Standard PO and GR/IR records into BW, but not the "DOWNPAYMENT POs" as they are stored in EKBE...

After initializing the Setup tables I found that those records are not getting pulled in the SETUP tables initialization process..

Can anyone help.

Thank You.

Rao

[Former Member]

hi

can you tell me which process key corresponds to,

sto glmng?(delivered qty)

[Former Member]

Hi Rao,

            Did you Find Out That is The Solution Because I am Also Facing Same Problem.

And Some Case If They Run MIRO Before MIGO Those Record Are Also Not Fetching In BI.

Thanks In Advance.

Praveen