Knowledge Management

Question:
Hi Gurus,
When we raise a PO for stockable item, at the time of GR, It picks up BSX and GBB keys to give debit and credit effects. I guess, this is depending upon the movement type(101). How SAP defines which keys to be used for debit credit for a perticuler movement type?
Sorry, I could not understand the screen in "OMWN" trx.
(Account grouping for movement types)
Can anyone explain please?
Regards,
Guest
Answer:
Hi,
When we raise a PO for stockable item, at the time of GR, It picks up BSX and GBB keys to give debit and credit effects
Unfortunately, your understanding is not correct. Once GR is posted, the value of stock movement will be debited to BSX with offsetting entry to WRX. Besides, it is also true to say that the Transaction OMWN will represent which Transaction/Event Key to be used for each and every movement type.
Cheers,
HT
_________________
Moderator:

Answer:
Hi Ha Tran,
Sorry, My mistake mentioning GR posting keys i.e. BSX and WRX.
My confusion is, when I check in OMWN trx, against movement type 101, I can not find any record where BSX or WRX is mentioned in field VORSL (Trx / event key). All rows are containing either KBS or PRD or GBB.
Still, it is picking the above trx / event keys for an item where material type is ROH and I leave the "Account assignment category" field in PO as blank.
How it is deriving it?
Regards,
Guest
Answer:
Hi,
In regard to movement type posting, there have been several scenarios for instance, GR with reference to PO, GR with reference to Order, even for the case of GR with reference to PO, difference should also be made where it is account assigned PO (usually for the case of non-stock) and standard PO (in regard to inventorized items). Therefore, to have a better understanding of how the automatic account assignment determination, you should go to Transaction OMWB where you can make your own simulation on how the automatic account determination is to be made. Let me know how it goes.
Cheers,
HT
_________________
Moderator:

Answer:
Hi Ha Tran,
I did the simulation for various material types. It showed me proper account in case of material type ROH. But, I created a material for type "HALB" for example and it showed me message "posting string for this scenario not found in table T156S"
I checked the table. It seems that, simulation programs checks this table with various parameters like Mov type, Movement indicator, receipt indicator and consumption indicator. (Though, I could not understand how the program derives these parameter values) and then check whether a row in available or not.
But, in this table, the posting strings available for val and qty have some values like "WE01", "ME01" etc. What is the meaning of this?
Where is the link between these posting strings and the actual posting event codes "BSX" and "WRX"?
Please reply
Regards
Guest
Answer:
Hi Ha Tran,
Please reply to my above post.
Thanks in advance
- Guest
Answer:
Pikoo
It is a good post. Even I was working on this since couple of days and couldn't understand completely.
Can some one who has good understanding on this topic explain the link between weo1, GBB and teh postings like BSX and WRX..
Thanks.
Answer:
Hi,
First of all, these terminology expressions and clarifications have been well provided in the training course LO550 and if you would have such training, then you would be clearly understanding about it. Due to the limitation of this posting, it is hardly possible for myself to clarify in details what value strings meant and why you would need such posting rule in account determination process in MM. However, what I can give you below are very fundamental definitions of what they meant in anticipation of providing a supplementary information in regard to this subject.
Basically in SAP, the posting transactions for the transactions in Inventory Management and Invoice Verification that are relevant for accounting are fixed. Posting records are assigned to each relevant movement type in Inventory Management and to each transaction in Invoice Verification. These posting records are generalized in a value string (posting rule). Instead of fixed G/L account numbers, this contains keys for the respective posting transactions (such as BSX for a stock posting and PRD for a price difference posting).
It is not necessary/mandatory for you to define these transaction keys, the R/3 system determines them from the transaction (in Invoice Verification) or from the movement type (in Inventory Management). It is only required to assign to each posting transaction the account to which it is posted. The assignment of value strings to goods movements and the breakdown of the value string into transaction keys can be seen in Customizing for Inventory Management and Physical Inventory, but it is not possible for you to change them.
The R/3 system automatically determines the value string assigned to a specific transaction. It depends partly on entered parameters manually and partly on parameters derived internally by the system.
An typical example is WE01 value string. In the standard system, the value string WE01 is assigned to goods receipts (and also cancellations and return deliveries) for Standard and Subcontracting purchase order items without account assignment concerning valuated material into stock.
Cheers,
HT
_________________
Moderator:

Answer:
Dear HaTran
Thank you so much for your explanation.
It definitely help us understanding the Automatic account assignment process.
Thanks