on 12-15-2006 6:06 PM
At my current client, there is the following situation in the BKPF table:
When the awtyp is 'BKPF' in the bkpf table, the awkey is number/company/year, as expected.
But when the awtyp is 'MKPF' in the bkpf table, the awkey is just number/year, with no intervening company code.
Is this standard practice for awkey in bkpf when awtyp = 'MKPF' ???
Or is this due to a configuration error that should be corrected ????
Hi,
Good morning and greetings,
That is standard SAP...If AWTYP is BKPF in the Object Key would be Document Number/Company Code/Year and in the case of MKPF it would be Document Number/Year as it pertains more to WA document type transaction which is from MM module and that is the reason the system will not be in a position to place the company code in the transaction.
Please reward points if found useful
Thanking you
With kindest regards
Ramesh Padmanabhan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Ramesh -
I thought that was the case, but wasn't sure.
It's a terrible practice, if you think about it.
If MM can't put a company in, then it should put in a ref nr followed by 4 spaces followed by the year.
That way, the awkey can always be queried with the expectation that the year wil be in the same place (bytes 15-18).
Anyway, thanks again for confirming what I thought.
Dave
User | Count |
---|---|
108 | |
12 | |
11 | |
6 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.