cancel
Showing results for 
Search instead for 
Did you mean: 

OBYC_integration

former_member219158
Participant
0 Kudos

Dear All,

When we post MIGO transaction....system automatically post the document based on OBYC settings

As it takes valuation class from material and select the GL account...

My question is --- in OBYC there are many transaction keys....how system picks transaction keys...logic??

Regards

Vijay

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Vijay,

At the time of MIGO, following Accounting Entry is posted:

Inventory A/C Dr.

      To GR/IR Account.

System determines the Inventory GL Account based on:

> Valuation class wise GL Accounts maintained in OBYC against transaction Key BSX.

> Valuation class maintained in Material master data.

Where as GR/IR Account is picked from OBYC > transaction key WRX.

Hope it helps.

Thanks

Harin Khakhkhar

former_member219158
Participant
0 Kudos

Dear Harin,

Yes i know based on Transaction key..BSX,,WRX..etc and then on valuation class system picks of GL accounts/....My question is how system picks Transaction keys ---whether to select BSX or WRX..anything else

Former Member
0 Kudos

Hi Vijay,

Depending on movement type ( including other parameters such as Spl stock indicator )and valuation class - accounts are determined).

Please find the below screenshot where transaction keys are assigned to movement type in T code OMJJ.

Thanks

Answers (8)

Answers (8)

former_member219158
Participant
0 Kudos

Thanks

Former Member
0 Kudos

Hi Vijay,

FI-MM integration can be achieved by combining the following - Valuation class and Movement Types.

Movement Types can be:

- BSX key is only for stock ie inventory posting

- WRX key is only for GR/IR clearing

- GBB key which takes care of most of remaining inventory postings

Freight charges (FR1,FR2 ETC) and others are not covered in GBB.

These are standard transaction keys provided by SAP.

We need to assign a G/L to each transaction type, for a valuation class.

Hope this helps.

Regards,

Aneesh

Former Member
0 Kudos

Hi Vijay,

Try to find out the use of OMWB, OMSK, OMWN, OMED and OBYC. you will have your answer how Account keys are picking at the time of Foods issue or any other transaction.

Take any PO number and see the Goods receipt and invoice receipt accounting document and see the logic on OMWB T code. you will see the GL account maintained.

Regards,

Sridhar

former_member191939
Active Contributor
0 Kudos

Hi Vijay,

In material master we maintain valuation class. Hence when
we do let us say GR for Purchase order

(101), the G/L account is decided as below:

Let us say movement type 101

Account modifier = space

Check in OBYC

As you are aware for any transaction there will be +ve and
-V entry in GL a/c Which a/c has to be -ve and which has to be + is decided by
posting key depending on transaction.

Hence When we do GR...Stock a/c will be +,
GR/IR will be -Ve and any price difference(if price control is -S) will be
posted to price difference account.

Inventory posting is done through BSX

Price difference will goto PRD

GR/IR will goto WRX

In OBYC, check the transaction BSX, for a given Chart of A/c,
for a given valuation modifier(it isnothing but plant grouping) and valuation
class, you can see the G/L account. This data is available in table T030

You can see the posting key for debit and cr. That means
when we do 101, then Stock will be credited and that posting key is used, if
you do reverse GR-102, then same stock a/c will get debited with that posting
key.

For the transaction PRD, you will get addition to the
above, one more column General modifier, this is nothing but the account
modifier in OMJJ for that movement type, i.e. Same transaction i.e. GR, if I
define a different account modifier, I can change the G/L account so that new
movement type PRD(variance) can be collected at different G/L account.

   

Like that WRX, in which it is maintained at client level no a/c modifier, no valuation class etc...that means GR/IR account determination will not depend onmovement type/material/plant etc.





Transaction/event key (internal processing key)





Posting transactions are predefined for those inventory
management and invoice verification transactions relevant to accounting.
Posting records, which are generalized in the value string, are



assigned to each relevant movement type in inventory
management and each transaction in invoice verification. These contain keys for
the relevant posting transaction (for example, inventory posting and
consumption posting) instead of actual G/L account numbers. You do not have to
define these transaction keys, they are determined automatically from the
transaction (invoice verification) or the movement type (inventory management).
All you have to do is assign the relevant G/L account to each posting
transaction.


Hope this Helps you out.


Regards,


Eugene



former_member219158
Participant
0 Kudos

Thanks to all for their inputs...

I am creating a new Transaction key - for our new business setup.

Now how to link the same to pick the GL while doing MIGO.

former_member211706
Participant
0 Kudos

I think it is not possible to creating a new transaction key for new business set up.please ask to sap regarding this issue.

regards

Pulak

former_member191939
Active Contributor
0 Kudos

Hi Vijay,

SAP strongly recommends not to create any transaction event type, I think exception is for some Unplanned Delivery costs.

Make use of available transaction event keys so that you will have a smooth process in account determination.

As required, just create for any specific business requirement & assigned to G/L account to new Trans./Event Key in OBYC.

Now you need to add new Trans./Event Key to respective condition type in MM pricing procedure in accruals column, so when you do transaction,. then respective G/L account will updated with new Trans./Event Key .

Regards

Eugene

former_member219158
Participant
0 Kudos

NO...its possible.

former_member211706
Participant
0 Kudos

Hi Vijay,

Sap designed the transaction key for FI-MM integration as per the business requirement in OBYC setting.

Before OBYC we have to do the assignment in OMSK

Process the object in specified sequence transaction OMSK

1-Account categories

2-Valuation class

3-matarial type/account categories reference.

As per your query you have to assign the GL account in the different transaction key automatic account assignment in background.

Without the GL account missing you cannot post any transaction fi-mm related.

So you have to assign the gl account for different transaction key.

Let me know for further query.

Regars

Pulak

former_member221187
Active Participant
0 Kudos

Hi vijay,

Based on moment type determine the predefined posting rules with combination of transaction key in valuation string.

Regards,

G Rajendhar.

former_member219158
Participant
0 Kudos

My question is how system picks transaction key..there are many keys in OBYC...

how system knows which one to pick up at what transactions...

Former Member
0 Kudos

Hi Vijay,

These are standard transaction keys and atandard configurations which are provided by SAP.

Thanks,

Harin Khakhkhar

former_member221187
Active Participant
0 Kudos

Hi  vijay,

Here it will take valuation class help valuation class link between material master and general ledger accounts in OBYC setting.

Regards,

G Rajendhar.

former_member221187
Active Participant
0 Kudos

Hi vijay,

FI-MM Integration is based on the following:

   Movement Types

   Valuation Class

   Transaction Keys

   Material Type

The Movement Type is the ‘classification key’ indicating the type of material movement (for

example, goods receipt, goods issue, physical stock transfer). The movement type enables the

system to find pre-defined posting rules determining how the accounts in FI (stock and

consumption accounts) are to be posted and how the stock fields in the material master record

are to be updated.

Figure

The Valuation Class refers to the assignment of a material to a group of GL accounts. Along with

other factors, the valuation class determines the GL accounts that are updated as a result of a

valuation-relevant transaction or event, such as a goods movement. The valuation class makes it

possible to:

   Post the stock values of materials of the same material type to different GL accounts.

   Post the stock values of materials of different material types to the same GL account.

The Transaction Key (also known as the ‘Event Key or Process Key’) allows users to

differentiate between various transactions and events (such as physical inventory transactions

and goods movements) that occur within the area of inventory management. The

transaction/event type controls the filing/storage of documents and the assignment of document

numbers.

The Material Type groups together materials with the same basic attributes, for example, raw

materials, semi-finished products, or finished products. When creating a material master record,

you must assign the material to a material type. The material type determines:

   Whether the material is intended for a specific purpose, for example, as a Configurable

Material or Process Material.

   Whether the material number can be assigned internally or externally.

   The Number Range from which the material number is drawn.

   Which screens appear and in what sequence.

   Which user department data you may enter.

   What Procurement Type the material has; that is, whether it is manufactured in-house or

procured externally, or both.

Together with the plant, the material type determines the material’s inventory management

requirement, that is:

   Whether changes in quantity are updated in the material master record.

   Whether changes in value are also updated in the stock accounts in financial accounting.

Regards,

G Rajendhar.

Former Member
0 Kudos

Vijay,

Account determination in the OBYC will be happened based on the movement type in corresponding with the transaction key. i.e. even in movement type we have movement indicator that will trigger the corresponding transaction key based on business transaction. Ex: 101 movement type is used for

A) Goods received from vendor to stock and

B) Goods received from production order to stock

Here, based on the movement indicator it will consider whether the stock comes from vendor or production order.

The link is below:

Every material is linked to the material type

Every material type is linked to accounting category

Every accounting category is linked to the valuation class

Every valuation class is linked to the material master in a plant.

BR, Srinivas Salpala

former_member211706
Participant
0 Kudos

Vijay

I will giving you one example that your question is how system picks transaction key..

If you take one transaction key BSX which is only for inventory posting, what are the inventory posting reflect the GL which you assign.

So  sap designed in such way which is automatically picks gl from that particular transaction.

Regards

Pulak

Former Member
0 Kudos

Dear Vijay,

As per business requirement, we have to select transaction key Ex- BSX,WRX,GBB, There are no link with many transaction key.  we are creating GL for GR/IR that we have to specify in respective transaction key,for that link only system is identifying.Please share still you have doubt.

with best regards-

prasanna

former_member191939
Active Contributor
0 Kudos

Hi Vijay,

  

The Movement type assigned to Transactions with the
General Modifiers will post to the assigned G/L Accounts

OBYC Settings for Account Modifier

In standard SAP, only three transaction
keys are having Account modifiers. The transaction keys are GBB, PRD, KON.

  

This account modifiers helps to post to
different G/L accounts for the same transaction event keys.

  

Account modifiers for GBB

  

AUA: for order settlement

AUF: for goods receipts for orders (without
account assignment)

and for order settlement if AUA is not
maintained

AUI: Subsequent adjustment of actual price
from cost center directly

to material (with account assignment)

BSA: for initial entry of stock balances

INV: for expenditure/income from inventory
differences

VAX: for goods issues for sales orders
without

account assignment object (the account is
not a cost element)

VAY: for goods issues for sales orders with

account assignment object (account is a
cost element)

VBO: for consumption from stock of material
provided to vendor

VBR: for internal goods issues (for
example, for cost center)

VKA: for sales order account assignment

(for example, for individual purchase
order)

VKP: for project account assignment (for
example, for individual PO)

VNG: for scrapping/destruction

VQP: for sample withdrawals without account
assignment

VQY: for sample withdrawals with account
assignment

ZOB: for goods receipts without purchase
orders (mvt type 501)

ZOF: for goods receipts without production
orders

  (mvt types 521 and 531)

 

Account Modifiers for KON

 

None for consignment liabilities

 

PIP for pipeline liabilities

Account modifiers for PRD

 

None for goods and invoice receipts against
purchase orders

PRF for goods receipts against production
orders and

order settlement

PRA for goods issues and other movements

PRU for transfer postings (price
differences in the case

  of external amounts)

Hope This Helps You,

 

Regards 

Eugene.

Former Member
0 Kudos

Hi Vijay,

As per the movement type system takes the transaction type.

T.code is OMWN.

Here all the combinations are existing.

Thanks.

former_member219158
Participant
0 Kudos

How system picks transaction keys.....BSX...WRX..

on what basis..???