Separate Transaction event key and Document type

Hello Gurus,
Need suggestion and process how to have separate transaction event key and Document types sued in Material document creation with a different number range for the movement types used for SD processes.
Example: 601/602/651 movement types have the Transaction event key as WL
561 has the Transaction event as WA
701/702 movement types have the Transaction event as WI
the transaction event keys of WA WH WI WL WQ WR WS WZ have the same number range.
I am looking for solution and suggestion as how do we maintain transaction event key and document type for SD dispatches, cancellation, returns movement types separately.
Thanks and Regards

Hi,
U can create new document type in OBF4 copy the existing on ee.g WA make new document type and in number range assign the FI number range which u want to assign, MM number range can be create in T. code OMBT and FI number range in FBN1. Documen ttype assignment to t. code is done in OMBA
regards,
zafar
Edited by: zafar_karnalkar on Aug 13, 2010 12:23 PM

Similar Messages

Posting Key and Document type

Hello,
I have just detected an inconsistency in one of my SAP environment (Development). I have an invoice posted from the SD module, document type of this invoice is RV.
If there is a reason to cancell this invoice, the transaction used is VF11. The document type in SD for this cancellation is S1. Thereafter an FI document is generated with document type AB.
Even though the settings in both Production and Acceptance and Developement are the same.
I have realised that the initial document when cancelled (reversed) has an FI document RV and posting key 11. whiles in customizing the settings for posting keys and document types are different from what has been customized. Below is my current settings.
The posting key 01 has a reversed posting key 12 and the document type RV has a reverse document type AB. This customizing is in correct in SPRO.
Transactions : OB41 and OBA7
Can anyone help on this....
Thanks
Elvis

Hello,
Did you verify whether AB document type in OBA7 is marked in "Account Types allowed" the Customer checkbox?
If not, maybe that is why it is not selecting AB as the reversal document type for RV, even though it is set up in RV document the AB document type as reverse document type.
Other than this (if the mentioned above doesn't solve your issue), I would say there should be any user-exit that can be changing the document type, according to some specific business rule of your SAP client or even a substitution.
I hope it helps you.
Regards,
Daniel.

Transaction event key and posting key

Dear All,
To create a new Transaction event key/posting key.Whats the T.code

Hi,
Follow the Path
SPRO-Materials Management-Purchasing-Conditions-Define Price Determination Process-Define Transaction/Event Keys
SPRO-Financial Accounting (New)-Accounts Receivable and Accounts Payable-Business Transactions-Internal Transfer Posting-Make and Check Document Settings-Define Posting Keys
Hope this finds useful.
Regards,
Vengat

About transaction /event keys

hi
mm gurus
for what type of transactions we will use GBB Transaction/event key and can u explain about the use of this
thanks
subbu

Hi
Offsetting entry for stock posting (GBB)
Offsetting entries for stock postings are used in Inventory Management. They are dependent on the account grouping to which each movement type is assigned. The following account groupings are defined in the standard system:
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)
regards
Srinivas

Transaction event key

Dear Sir,
Thanks for reply
ho to create transaction event key for movment type 201,
Regards,
Mukesh

Hi
SAP recommends not to change any standard movement type.
Copy the movement type 201 and create a new movement type Z21 and change the transaction key there using transaction OMJJ.
Transaction keys can be created in SPRO-IMG-MM-Purchasing-Conditions-Define Price Determination Process-> Define Transaction/Event Keys
Thanks & Regards
KK

G/L account change for existing VAX trans event key(601 movement type)

Hi experts,
My client wants to post the sales(VAX transaction event key for movement type 601) of a material into new G/L account than the existing one. They dont want to create a new Material type & Valuation class for the same.
I suggested to create a new class for the existing material type and use the same in OBYC, but they dont want to create the new valuation class.
Is there any way do that? pls suggest.
Regards
Srin.

Hi,
COGS account is always against the Inventory account of the goods Purchased.
Without raw material account how the consumption account will hit in to the another account or 2 account.
x: if your one of material Inventory G/Laccount is : 99999
the same you have COGS account in GBB-VAX : 77777
When you make sales the Inventory get reduced/consumed against the COGS account.
How the system allow you to post in One more account.
Else you suggest them to chage the existing G/L account.
Clear with out Inventory account you can't use one more COGS account.
SAM

Linkage of transaction event key with new movement type

Hello All,
I have have created a new Z movement type and 1 new Transaction event key. I have to link my new Transaction event key with my new Movement type. That i can see in OBYC.
Please tell me How can i do it.
Regards,
Vishal Garg
Edited by: vishal garg on Sep 27, 2010 2:43 PM

Simple way is, check the TEK of existing movement type & it's assignment in OBYC.
Now You will be able to decide how your postings can be done.
I hope you have copied the movement type & then replaced it's TEK & account modifier according to your requirement.
Regards,
Piyush

Exise Transaction type and Document Type for part 2 record created by J2iun

Hi All ,
We utilized available credit of SERVICE TAX (HCESS and ECESS) and CENVAT (of both RG23A and RG23C) credit against payable SERVICE TAX ( ECESS and HCESS).
At the time of save , system has generated accounting document.I have checked generated accounting document which is perfect.Here the document type selected by the system is ED.
But when I check corresponding part2 entry (in table J_1IPART2) there system has not updated any value in fields Exise Transaction Type (TT) and document Type while internal document and Financial Year are updated with 0 value.
I am not sure if system behaves in the same way for J2IUN generated PART-2 entry.
I need your help to understand it.
Regards
Shrey

Hi,
There is not any transaction type for Excise Utilization and determining the accounts of the fortnightly utilization.
The credit account of the transaction type u2018DLFCu2018 is used as the debit account here. For the credit side we pick the debit accounts from the GRPO, EWPO and TR6C transactions.
This is the reason system only generates a Part II Serial No and updates in table.

Business Transaction event keys.

Hi,
Other than GBB, what are all the other business event keys ( eg. PRD, KON ) for which account modifier is possible. and what is the functionality behind this.
Regards,
RitiG

Hi Ritigo
Offsetting entry for stock posting (GBB)
Offsetting entries for stock postings are used in Inventory Management. They are dependent on the account grouping to which each movement type is assigned. The following account groupings are defined in the standard system:
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)
You can also define your own account groupings. If you intend to post goods issues for cost centers (mvt type 201) and goods issues for orders (mvt type 261) to separate consumption accounts, you can assign the account grouping ZZZ to movement type 201 and account grouping YYY to movement type 261.
Other than GBB there many other transaction event keys:
you can go to Tcode OBYC and see there...for eg.purpose i'll tell u the imp. one
Agency business: income (AG1)
This transaction can be used in agency business for income deriving from commission (e.g. del credere commission). The account key is used in the calculation schemas for agency business to determine the associated revenue accounts.
Agency business: turnover (AG2)
This transaction can be used in agency business if turnover (business volume) postings are activated in Customizing for the payment types. The account key is specified in Customizing for the billing type.
Agency business: expense (AG3)
This transaction can be used in agency business for commission expenses. The account key is used in the calculation schemas for agency business to determine the associated expense accounts.
Expense/revenue from consumption of consignment material (AKO)
This transaction is used in Inventory Management in the case of withdrawals from consignment stock or when consignment stock is transferred to own stock if the material is subject to standard price control and the consignment price differs from the standard price.
Expenditure/income from transfer posting (AUM)
This transaction is used for transfer postings from one material to another if the complete value of the issuing material cannot be posted to the value of the receiving material. This applies both to materials with standard price control and to materials with moving average price control. Price differences can arise for materials with moving average price if stock levels are negative and the stock value becomes unrealistic as a result of the posting. Transaction AUM can be used irrespective of whether the transfer posting involves a transfer between plants. The expenditure/income is added to the receiving material.
Supplementary entry for stock (BSD)
This account is posted when closing entries are made for a cumulation run. This account is a supplementary account to the stock account; that is, the stock account is added to it to determine the stock value that was calculated via the cumulation. In the process, the various valuation areas (for example, commercial, tax), that are used in the balance sheet are taxed separately.
Change in stock (BSV)
Changes in stocks are posted in Inventory Management at the time goods receipts are recorded or subsequent adjustments made with regard to subcontract orders.
If the account assigned here is defined as a cost element, you must specify a preliminary account assignment for the account in the table of automatic account assignment specification (Customizing for Controlling) in order to be able to post goods receipts against subcontract orders. In the standard system, cost center SC-1 is defined for this purpose.
Stock posting (BSX)
This transaction is used for all postings to stock accounts. Such postings are effected, for example:
In inventory management in the case of goods receipts to own stock and goods issues from own stock
In invoice verification, if price differences occur in connection with incoming invoices for materials valuated at moving average price and there is adequate stock coverage
In order settlement, if the order is assigned to a material with moving average price and the actual costs at the time of settlement vary from the actual costs at the time of goods receipt
Because this transaction is dependent on the valuation class, it is possible to manage materials with different valuation classes in separate stock accounts.
Price differences (PRD)
Price differences arise for materials valuated at standard price in the case of all movements and invoices with a value that differs from the standard price. Examples: goods receipts against purchase orders (if the PO price differs from the standard pricedardpreis), goods issues in respect of which an external amount is entered, invoices (if the invoice price differs from the PO price and the standard price).
Price differences can also arise in the case of materials with moving average price if there is not enough stock to cover the invoiced quantity. In the case of goods movements in the negative range, the moving average price is not changed. Instead, any price differences arising are posted to a price difference account.
Depending on the settings for the posting rules for transaction/event key PRD, it is possible to work with or without account modification. If you use account modification, the following modifications are available in the standard system:
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)
Revenue/expense from revaluation (UMB)
This transaction/event key is used both in Inventory Management and in Invoice Verification if the standard price of a material has been changed and a movement or an invoice is posted to the previous period (at the previous price).
Expenditure/income from revaluation (UMD)
This account is the offsetting account for the BSD account. It is posted during the closing entries for the cumulation run of the material ledger and has to be defined for the same valuation areas.
Price differences (PRD)
Price differences arise for materials valuated at standard price in the case of all movements and invoices with a value that differs from the standard price. Examples: goods receipts against purchase orders (if the PO price differs from the standard pricedardpreis), goods issues in respect of which an external amount is entered, invoices (if the invoice price differs from the PO price and the standard price).
Price differences can also arise in the case of materials with moving average price if there is not enough stock to cover the invoiced quantity. In the case of goods movements in the negative range, the moving average price is not changed. Instead, any price differences arising are posted to a price difference account.
Depending on the settings for the posting rules for transaction/event key PRD, it is possible to work with or without account modification. If you use account modification, the following modifications are available in the standard system:
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)
Regards
Yogesh

Where to change posting key for Document type RG?

Hi ,
May I know where is IMG path to change posting key for Document type RG?
Thanks.

Hi,
Posting key is not assigned to the document types.
Posting key can be assigned to a particular trnsaction event etc., for example in OB40 for each transaction key in tax area, you can ddefine the posting key for bedit and credit.
However you have the option to create a validation to check that this particular document type is allowed to be posted with certain posting keys. Validation can be created in OB28, GGB0. The details are available in SDN. Please search that.
Regards,
Gaurav

Different GL for Transaction/Event Key FRL

Hi expert,
I hv an issue for subcontract processing.. as defined in SAP the GL for Subcontract is :
Dr. [FRL] External Service Fee
Cr. [WRX] GR/IR
Dr. [GBB-VBO] Inventory
Cr. [BSV] SP components for refurbishment
but at the other requirement, the GL for subcontract need to define as the following :
Dr. [FRL] External Service Material
Cr. [WRX] GR/IR
Dr. [GBB-VBO] Inventory
Cr. [BSV] SP components for refurbishment
So, how can i define the differences. As i know, SAP just give one transaction/key FRL with one GL account.
Is there any solutions for this issue?
i think that it can be changed by defining a new mov.type copy from 101 to combine with new transaction/event key to differ the GL account, but the matter is i can't find any acc.modification FRL assign in this mov.type so i can't change it with new transaction/event key on it....
please help mee...
Regards,
AJ

Dear Kumar,
i ll explain it more details..
the material is the same.. the business process is that the material can be repaired and can be buy by using procedure exchange parts program.
when it is repaired.. the requirement for the GL is :
Dr. FRL External Service Fee
Cr. WRX GR/IR
Dr. GBB-VBO Inventory
Cr. BSV SP components for refurbishment
and when it is exchanging parts program the GL is :
Dr. FRL External Service Material
Cr. WRX GR/IR
Dr. GBB-VBO Inventory
Cr. BSV SP components for refurbishment
and certainly, the material can only be assigned with one valuation class.. logically one valuation class can't be assigned with more than one GL account in one trans/event key especially FRL..
So how it can be solved? or is there any solution by creating a new movement type for Godds Receipt to move the GL to another one.. thanks

Transaction Event Keys in MIGO

Dear Experts,
In 4.6 or 4.7 version in display accounting document after making MIGO transaction I was able to view account transaction event keys, like BSX, WRX, FRL etc. But in 5.0 I am not able to view, even after selecting in change layout. But I can view the GL account no. If any one knows to view this event keys kindly let me know. And please inform is it possible or not in 5.0.
regards,
Madhu

HI MADHU,
PLS FOLLOW THE FOLLOWING PROCESS AFTER POSTING A MIGO:
DISPLAY>>MATERIAL DOCUMENT NO.>.ENTER>.DOC. INFO.>>GOTO AT THE HEADER WHERE U CAN FIND DOCUMENT>>IN DOCUMENT CHOOSE PRINT PREVIEW>>HERE U CHOOSE CHANGE CURRENT LAYOUT>>FROM HIDDEN FIELD CHOOSE TRANSACTION AND BRING IT TO LINE 1>>CHOOSE COPY.
PLS REWARD IF FOUND USEFUL.
REGARDS,
INDRANIL

Regarding Delivery and document type

Hi Gurus,
I copied both the delivery type and document type from NL and UB and I also assigned delivery type and checking rule to the supplying plant in SPRO- LE - MM- PUR- PO - set up STO. and also assigned the Document type in SPRO- LE - MM- PUR- PO - set up STO assign doc type, one step....
But when I create the STO the system issues a warning message that
Doc. type YUB should be used for suppl. plant XXXX and receiving plant XXXX
Message no. 06674
can you please give me some suggestions
Shane

Hi narayan,
I am working with INTRA company STO and I have checked with the config what i have did again and now I can get the shipping tab.............. only thing is before I have forgot to assign the Issuing storage location in the transaction process. So now i can create a STO.
Now I am not sure how and where we need to make changes so that the process doesnt ask for Issuing storage location information and still create the STO between two plants in a same company.
Thank you for your responses. They really helped me in figuring where exactly i am going wrong
Shane

SAP Easy DMS - Link between Document Area and Document Types

Deat Friends,
Is there a transaction code or a customizing available to link the Document Area and Document Types??
For example: Document Area (DMS) is linked with Document Type (DRW)
Thank you,
Sri

Hello Chandu,
We are trying to create a documents via TCODE: CVO1N
One of the entry we need to populate is the "DOCUMENT TYPE" to create a document. If, we enter the Document Type = DRW, we are not able to see our custom Storage Category while attaching/Check-in a document.
Where as, If, we enter the Document Type = DMO, we are able to see our custom Storage Category while attaching/Check-in a document.
I see that the Document Type = DRW is linked to Document Area = DMS
Similarly, the Document Type = DMO is linked to Document Area = FILESYSTEM
My question is, Is there a transaction code or a customizing option available to link the Document Area and Document Type?
Thank you,
Sri

No archive information found for object type and document type

Hi All,
When i try to view the print preview for a perticular doc type, system is giving the error as "No archive information found for object type and document type"
Diagnosis
    No information was found about optical archiving. This may be due to
    either of the following reasons:
    1. No valid archiving parameters were passed
    2. Your system is not configured for optical archiving
System Response
    Processing is cancelled.
Procedure
    Specify valid archiving parameters or check whether your system is configured for optical archiving
Regds,
CB

Hello,
You are trying to Print & also archive by selecting the option Print & Archive.
You have to do archivelink configurations and then create document type and assign to the object type with content repository with archivelink table.
If you want to archive the spool or output then you have to use object type as DRAW. If you are archiving invoice document or letters or so on then you have to know the object type/Business object of the transaction.
Please note that for archivelink configuration, attachment will be either stored in archive server or in SAP database table based on business requirement.
Hope this will give you some understanding on archiving area.
-Thanks,
Ajay

Separate Transaction event key and Document type

Similar Messages

Maybe you are looking for