Busniees Transaction COC

Hi Gurus ,
I have run CKMLCP month of FEB i am getting error at the time of post-closing system asked COC bus. Transaction
My doubt this bus. Transaction need for COGS na .At that time I mapped to COC in OBYC .
what ever I mapped for PRY GL account 524002 .i am using same GL account 524002 for COC.
my doubt Which GL account map in COC and what are posting key using to debit and credit.
What time COC bus. Transaction need please tell me and which GL map to COC.
Regards,
gopi.

Go to OBYC/COC/Chart of accounts/Valuation class and enter GL accounts
Revaluation of other consumption (COC)
This transaction/event key is required for the revaluation of consumption in Actual Costing/Material Ledger.
Revaluation of consumption valuates single-level consumption using the actual prices determined in the Actual Costing/Material Ledger
application. This revaluation can either take place in the account where the original postings were made, or in a header account.
The header account is determined using the transaction/event key COC.

Similar Messages

Query on Material Ledger

Hi All,
Configuration settings:
1. Movement Type (MT) 201 is assigned to Movement Type Group(MTG) CC to revalue FI/CO accounts
2. MT 202 is not assigned to any MTG
Scenario:
1. Post MT 201 to cost center
2. Post MT 202 to cost center(reversal)
3. Run CKMLCP
4. MT201 revalued to cost center
5. MT202 not revalued to cost center > post to OBYC - Transaction COC
Since we need MT202 to revalue to cost center, we did the following:
6. Reverse the CKMLCP run
7. Change configuration > assign MT 202 to MTG CC
8. Run CKMLCP again
9. MT201 revalued to cost center
10. MT202 not revalued to cost center > post to OBYC - Transaction COC
Looks like if the posting done before the configuration, the settings for MT & MTG is not effective. Can anyone confirm whether faced the similar scenario before and what is the resolution for it?
We need to the "revaluation of consumption" in CKMLCP post to cost center for MT201 & MT202.

Hi Raj,
unfortunately your conclusion is right: The revaluation of consumption is dependent on the info that was collected during the month, when the actual material movements took place. When mvt 202 had no movement type group then, CKMLCP will not be able to revalue the cost of consumption for that. There is no possibility to adjust that after the fact, besides manual correction postings.
best regards,
Udo

COC at the time of run CKMLCP transaction

Hi, Experts
When we run CKMCLP for period "7" with the parameter select "Revaluation Material, Revaluation Consumption and Set CO A/c.Assignment", the system ask COC transaction event key for finished material which valuation class is 7920, my question is the COC transaction event key use for consumption account for ROG and SFG, So why system ask COC for FG material,
Account determination for entry 9000 COC 0001 ___ 7920 not possible
Message no. M8147
The system did not find an account for this transaction. This means that the account determination for key 9000 COC 0001 ___ 7921 is not maintained in MM Customizing (Valuation). The key is made up of:
Chart of account
Transaction key (= Posting transaction)
Valuation grouping code
Account grouping code
Valuation class
System Response
The system cannot update a G/L account for this transaction. You cannot post the transaction.
Procedure
Contact your system administrator.
If you have the authorization, check the Account determination in Customizing for Valuation.
Proceed
Note
The relevant posting transaction can be found in Table T030A.
Kindly help to solve the issue
Thanks & Regards,

Go to OBYC/COC/Chart of accounts/Valuation class and enter GL accounts
Revaluation of other consumption (COC)
This transaction/event key is required for the revaluation of consumption in Actual Costing/Material Ledger.
Revaluation of consumption valuates single-level consumption using the actual prices determined in the Actual Costing/Material Ledger
application. This revaluation can either take place in the account where the original postings were made, or in a header account.
The header account is determined using the transaction/event key COC.

Digital/Electronic signature in CoC(certificate of compliance)

Hi PP Gurus,
The user has requested to enter Digital/Electronic signature in Certificate of Compliance (CoC). CoC is previewed and printed from transaction QC20.
Please throw some light on this as I dont have knowledge regarding Digital/Electronic Signature.
Its urgent. Thanks.
Regards,
Rakesh Wade.

Dear Rakseh,
maybe note 700495 can help you here, the note has an PDF document which provide an implementation guide of digital signature-tool.
Regards,
Sabine

Regarding Transaction type (TTY) and Movement type for MM (OBYC)

Hi SAP Expers,
In company's monthly rollup I am not seeing transcation type in some of the accounts. These accounts belogs to Account Assingment in OBYC. There is movement type and TTY for transaction. I am trying to get if movement type 101 is there accounting entry will display 09 in accounting document. I am not able to get that. Please check below attached mention screen shot. Please guide me step by step how should I will get required information.
Plse check file the field TTY for particular account shows blank. we want it display tty such as 01,09,02,and many more tty which related to particular account plse check attachment for that. and please guide me if you know what configuration I should check. This account belogs to material management

Hi Mona,
Not sure if this helps:
The OBYC relates to Transaction Keys = BSX/COC/GBB. These are updated in Field KTOSL.
The Field in Screen most probably relates to BEWAR.
In case the business scenario relates to Consolidation then the "Transaction-field" that is seen in screen may relate to cusomization mentioned below
S_ALR_87002588 - Maintain Transaction Types for Consolidation
S_ALR_87002594 - Assign Asset Transaction Types
Navigation: Enterprise Controlling - Consolidation - Integration: Preparation for Consolidation - Preparation in the Sender System - Preparations Related to All Consolidation Types - Transaction Type Account Assignment
Regards
Satya

Please help me in ABAP coding for the incoming transactional data

Hi
I have the following transactional data
Transaction ID- Buyer- Seg- Fam- Cla -Com-Total
00001 - AB co - Engineering - Machinery - Equipment - Mechanical -15000
00002 - AC co - Engineering - Machinery - Equipment - Mechanical -15850
00003 - DE co - IT - Hardware - Mouse -Optical -5850
00004 - AC co - Engineering - Machinery - Equipment - Architectural -10000
00005 - FE co - Engineering - Machinery - Equipment - NOT_KNOWN -1580
00006 - KC co - Engineering - Machinery - Equipment - NOT_KNOWN -75850
00007 - EG co - Engineering - Machinery - Equipment - Mechanical -180050
00008 - AS co- Engineering - Machinery - Equipment - Architectural -10550
00009 - DE co - IT - Hardware - Mouse -Optical -58500
00010 - EF co - IT - Hardware - Mouse -NOT_KNOWN -555850
00011 - EF co - Engineering - Machinery - Equipment - Mechanical -44850
00012 - AC co - IT - Hardware - NOT_KNOWN -NOT_KNOWN -585550
In this transactional data, SEG-> FAM -> CLA -> COM are in hierarchy
To distiguish the NOT_KNOWN which have different level i like to change there names like this...
NOT_KNOWN_1, NOT_KNOWN_2....like that
I expect the results to be like this
Transaction ID- Buyer- Seg- Fam- Cla -Com-Total
00001 - AB co - Engineering - Machinery - Equipment - Mechanical -15000
00002 - AC co - Engineering - Machinery - Equipment - Mechanical -15850
00003 - DE co - IT - Hardware - Mouse -Optical -5850
00004 - AC co - Engineering - Machinery - Equipment - Architectural -10000
00005 - FE co - Engineering - Machinery - Equipment - NOT_KNOWN_1 -1580
00006 - KC co - Engineering - Machinery - Equipment - NOT_KNOWN_1 -75850
00007 - EG co - Engineering - Machinery - Equipment - Mechanical -180050
00008 - AS co- Engineering - Machinery - Equipment - Architectural -10550
00009 - DE co - IT - Hardware - Mouse -Optical -58500
00010 - EF co - IT - Hardware - Mouse -NOT_KNOWN_2 -555850
00011 - EF co - Engineering - Machinery - Equipment - Mechanical -44850
00012 - AC co - IT - Hardware - NOT_KNOWN_3 -NOT_KNOWN_4 -585550
I like to make this changes in the coming data by writing a start routine
Could anyone provide me the required code to make this happen
Plz help me
Regards
KC

Hi
My Start routine screen look like this
Declaration of transfer structure (selected fields only)
TYPES: BEGIN OF TRANSFER_STRUCTURE ,
Record number to be filled in case of adding row(s)
to enable 'error handling'
    record      TYPE rsarecord,
InfoObject TRAID: CHAR - 000060
    /BIC/TRAID(000060) TYPE C,
InfoObject SEG5: CHAR - 000060
    /BIC/SEG5(000060) TYPE C,
InfoObject FAM5: CHAR - 000060
    /BIC/FAM5(000060) TYPE C,
InfoObject CLA5: CHAR - 000060
    /BIC/CLA5(000060) TYPE C,
InfoObject COM5: CHAR - 000032
    /BIC/COM5(000032) TYPE C,
InfoObject COCE: NUMC - 000015
InfoObject TOTALSEG: CHAR - 000032
    /BIC/TOTALSEG(000032) TYPE C,
END OF TRANSFER_STRUCTURE .
Is this information you are lookin or something more
Regards
KC

OBYC-COC (Revaluation of "other" consumptions)

Hi Gurus,
i want to know about standard posting key for transaction key COC & impact to transaction, anybody can explain to me about this....Pliiiiz.
Thanks,
ARA
Note for COC :
This transaction/event key is only relevant to Brazil. It is used if a revaluation report is used for company
codes in Brazil.
The revaluation report uses the actual prices determined by the material ledger/actual costing to:
u2022Revaluate costs on the basis of actual prices
u2022Post the price differences arising from "other" consumptions (e.g. consumption to cost
center) to a collective account
This transaction/event key is needed to post the price differences. The account specified here is posted
with the price differences for "other" consumptions.

Dear Friend
Revaluation of other consumption (COC)
This transaction/event key is required for the revaluation of consumption in Actual Costing/Material Ledger.
Revaluation of consumption valuates single-level consumption using the actual prices determined in the Actual Costing/Material Ledger application. This revaluation can either take place in the account where the original postings were made, or in a header account.
The header account is determined using the transaction/event key COC.
regards
pramod

Transaction Keys Description in MM(BSX, GBB etc)

Hi all,
I was going through many documents for FI/MM Integration but i could not understand what exactly are these transaction keys used for. for ex if thr is a movement type 101, GR agnst PO. then we have two things to do go to BSX- give the debit account and go to GBB-AUM to credit, if i am not wrong. I appreciate if someone please explain the usage in normal terms quoting some examples.
Thanks
Shriya

Hi,
some of the key descriptions -
Expense/revenue from consumption of consignment material (AKO)
 Expenditure/income from transfer posting (AUM)
 Provisions for subsequent (end-of-period rebate) settlement (BO1)
 Income from subsequent settlement (BO2)
 Income from subsequent settlement after actual settlement (BO3)
 Change in stock (BSV)
 Stock posting (BSX)
Revaluation of "other" consumptions (COC)
 Small differences, Materials Management (DIF)
 Purchase account(EIN), purchase offsetting account (EKG), freight purchase account (FRE)
External service (FRL)
External service, delivery costs (FRN)
Offsetting entry for stock posting (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)
Regards,
Sridevi
* Pls. assign points, if useful
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/sridevi+pattabiraman">me!</a>

OBYC- GBB- Transaction keys

hi
Can any one tell me what are these keys meant for
In GBB: AUA,AUF,BSA,INV,VBR,VAX,VAY,ZOF,ZOP are some of the keys I have mentioned.
I want to know to which key I have assign the inventory,scrap,consumption G/L codes ,etc for process industry in repetitive and discrete manufacturing scenario.

Hi,
Check this..
     Transactions
     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.
     Provisions for subsequent (end-of-period rebate) settlement (BO1)
     If you use the "subsequent settlement" function with regard to conditions (e.g. for period-end volume-based rebates), provisions for accrued income are set up when goods receipts are recorded against purchase orders if this is defined for the condition type.
     Income from subsequent settlement (BO2)
     The rebate income generated in the course of "subsequent settlement" (end-of-period rebate settlement) is posted via this transaction.
     Income from subsequent settlement after actual settlement (BO3)
     If a goods receipt occurs after settlement accounting has been effected for a rebate arrangement, no further provisions for accrued rebate income can be managed by the "subsequent settlement" facility. No postings should be made to the account normally used for such provisions. As an alternative, you can use this transaction to post provisions for accrued rebate income to a separate account in cases such as the one described.
     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.
     Caution
     Take care to ensure that:
     A stock account is not used for any transaction other than BSX
     Postings are not made to the account manually
     The account is not changed in the productive system before all stock has been booked out of it
     Otherwise differences would arise between the total stock value of the material master records and the balance on the stock account.
     Account determination of valuated sales order stock and project stock
     Note that for valuated sales order stock and project stock (special stock E and Q) and for the transaction/event keys BSX andGBB, you must maintain an account determination to avoid receiving warning messages when entering data (purchase order or transfer posting) for valuated stock.
     During data entry, the system attempts to execute a provisional account determination for GBB for valuated stock. The system will only replace the provisional account determination for GBB with the correct account determination for the stock account (BSX), in the background, if you enter the data for valuated stock at a later point in time.
     Revaluation of other consumption (COC)
     This transaction/event key is required for the revaluation of consumption in Actual Costing/Material Ledger.
     Revaluation of consumption valuates single-level consumption using the actual prices determined in the Actual Costing/Material Ledger application. This revaluation can either take place in the account where the original postings were made, or in a header account.
     The header account is determined using the transaction/event key COC.
     Del credere (DEL)
     Transaction/event key for the payment/invoice list documents in Purchasing. The account key is needed in the calculation schema for payment/settlement processing to determine the associated revenue accounts.
     Small differences, Materials Management (DIF)
     This transaction is used in Invoice Verification if you define a tolerance for minor differences and the balance of an invoice does not exceed the tolerance.
     Purchase account(EIN), purchase offsetting account (EKG), freight purchase account (FRE)
     These transactions are used only if Purchase Account Management is active in the company code.
     Note
     Due to special legal requirements, this function was developed specially for certain countries (Belgium, Spain, Portugal, France, Italy, and Finland).
     Before you use this function, check whether you need to use it in your country.
     Freight clearing (FR1), provision for freight charges (FR2), customs duty clearing (FR3), provision for customs duty (FR4)
     These transactions are used to post delivery costs (incidental procurement costs) in the case of goods receipts against purchase orders and incoming invoices. Which transaction is used for which delivery costs depends on the condition types defined in the purchase order.
     You can also enter your own transactions for delivery costs in condition types.
     External service (FRL)
     The transaction is used for goods and invoice receipts in connection with 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.
     External service, delivery costs (FRN)
     This transaction is used for delivery costs (incidental costs of procurement) in connection with 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.
     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.
     Caution
     If you use goods receipts without a purchase order in your system (movement type 501), you have to check to which accounts the account groupings are assigned ZOB
     If you expect invoices for the goods receipts, and these invoices can only be posted in Accounting, you can enter a clearing account (similar to a GR/IR clearing account though without open item management), which is cleared in Accounting when you post the vendor invoice.
     Note that the goods movement is valuated with the valuation price of the material if no external amount has been entered.
     As no account assignment has been entered in the standard system, the assigned account is not defined as a cost element. If you assign a cost element, you have to enter an account assignment via the field selection or maintain an automatic account assignment for the cost element.
     Account determination of valuated sales order stock and project stock
     Note that for valuated sales order stock and project stock (special stock E and Q) and for the transaction/event keys BSX andGBB, you must maintain an account determination to avoid receiving warning messages when entering data (purchase order or transfer posting) for valuated stock.
     During data entry, the system attempts to execute a provisional account determination for GBB for valuated stock. The system will only replace the provisional account determination for GBB with the correct account determination for the stock account (BSX), in the background, if you enter the data for valuated stock at a later point in time.
     Purchase order with account assignment (KBS)
     You cannot assign this transaction/event key to an account. It means that the account assignment is adopted from the purchase order and is used for the purpose of determining the posting keys for the goods receipt.
     Exchange Rate Differences Materials Management(AVR) (KDG)
     When you carry out a revaluation of single-level consumption in the material ledger for an alternative valuation run, the exchange rate difference accounts of the materials are credited with the exchange rate differences that are to be assigned to the consumption.
     Exchange rate differences in the case of open items (KDM)
     Exchange rate differences in the case of open items arise when an invoice relating to a purchase order is posted with a different exchange rate to that of the goods receipt and the material cannot be debited or credited due to standard price control or stock undercoverage/shortage.
     Differences due to exchange rate rounding, Materials Management (KDR)
     An exchange rate rounding difference can arise in the case of an invoice made out in a foreign currency. If a difference arises when the posting lines are translated into local currency (as a result of rounding), the system automatically generates a posting line for this rounding difference.
     Exchange Rate Differences from Lower Levels (KDV)
     In multi-level periodic settlement in the material ledger, some of the exchange rate differences that have been posted during the period in respect of the raw materials, semifinished products and cost centers performing the activity used in the manufacture of a semifinished or finished product are debited or credited to that semifinished or finished product.
     Consignment liabilities (KON)
     Consignment liabilities arise in the case of withdrawals from consignment stock or from a pipeline or when consignment stock is transferred to own stock.
     Depending on the settings for the posting rules for the transaction/event key KON, it is possible to work with or without account modification. If you work with account modification, the following modifications are available in the standard system:
     None for consignment liabilities
     PIP for pipeline liabilities
     Offsetting entry for price differences in cost object hierarchies (KTR)
     The contra entry for price difference postings (transaction PRK) arising through settlement via material account determination is carried out with transaction KTR.
     Accruals and deferrals account (material ledger) (LKW)
     If the process of material price determination in the material ledger is not accompanied by revaluation of closing stock, the price and exchange rate differences that should actually be applied to the stock value are contra-posted to accounts with the transaction/event key LKW.
     If, on the other hand, price determination in the material ledger is accompanied by revaluation of the closing stock, the price and exchange rate differences are posted to the stock account (i.e. the stock is revalued).
     Price Difference from Exploded WIP (Lar.) (PRA)
     If you use the WIP revaluation of the material ledger, the price variances of the exploded WIP stock of an activity type or a business process are posted to the price differences account with transaction/event key PRA.
     Differences (AVR Price) (PRC)
     In the alternative valuation run in the material ledger, some of the variances that accrue interest in the cost centers, are transfer posted to the semifinished or finished product.
     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)
     Price Differences (Material Ledger, AVR) (PRG)
     When you carry out a revaluation of single-level consumption in the material ledger during the alternative valuation run, the price difference accounts of the materials are credited with the price differences that are to be assigned to the consumption.
     Price differences in cost object hierarchies (PRK)
     In cost object hierarchies, price differences occur both for the assigned materials with standard price and for the accounts of the cost object hierarchy. In the course of settlement for cost object hierarchies after settlement via material account determination, the price differences are posted via the transaction PRK.
     Price Difference from Exploded WIP (Mat.) (PRM)
     If you use the WIP revaluation of the material ledger, the price and exchange rate differences of the exploded WIP stock of a material are posted to the price difference account with transaction/event key PRM.
     Price differences, product cost collector (PRP)
     During settlement accounting with regard to a product cost collector in repetitive manufacturing, price differences are posted with the transaction PRP in the case of the valuated sales order stock.
     This transaction is currently used in the following instances only:
     - Production cost collector in Release 4.0
     - Product cost collector in IS Automotive Release 2.0 (product cost collector in connection with APO)
     Offsetting entry: price differences, product cost collector (PRQ)
     The offsetting (contra) entry to price difference postings (transaction PRP) in the course of settlement accounting with respect to a product cost collector in repetitive manufacturing in the case of the valuated sales order stock is carried out via transaction PRQ.
     This transaction is currently used in the following instances only:
     - Production cost collector in Release 4.0
     - Product cost collector in IS Automotive Release 2.0 (product cost collector in connection with APO)
     Price Differences from Lower Levels (PRV)
     In multi-level periodic settlement in the material ledger, some of the price differences posted during the period in respect of the raw materials, semifinished products, and cost centers performing the activity used in a semifinished or finished product, are transfer posted to that semifinished or finished product.
     Price differences for material ledger (PRY)
     In the course of settlement in the material ledger, price differences from the material ledger are posted with the transaction PRY.
     Expense and revenue from revaluation (retroactive pricing, RAP)
     This transaction/event key is used in Invoice Verification within the framework of the revaluation of goods and services supplied for which settlement has already taken place. Any difference amounts determined are posted to the accounts assigned to the transaction/event key RAP (retroactive pricing) as expense or revenue.
     At the time of the revaluation, the amounts determined or portions thereof) are posted neither to material stock accounts nor to price difference accounts. The full amount is always posted to the "Expense from Revaluation" or "Revenue from Revaluation" account. The offsetting (contra) entry is made to the relevant vendor account.
     Invoice reductions in Logistics Invoice Verification (RKA)
     This transaction/event key is used in Logistics Invoice Verification for the interim posting of price differences in the case of invoice reductions.
     If a vendor invoice is reduced, two accounting documents are automatically created for the invoice document. With the first accounting document, the amount invoiced is posted in the vendor line. An additional line is generated on the invoice reduction account to partially offset this amount. With the second accounting document, the invoice reduction is posted in the form of a credit memo from the vendor. The offsetting entry to the vendor line is the invoice reduction account. Hence the invoice reduction account is always balanced off by two accounting documents within one transaction.
     Provision for delivery costs (RUE)
     Provisions are created for accrued delivery costs if a condition type for provisions is entered in the purchase order. They must be cleared manually at the time of invoice verification.
     Taxes in case of transfer posting GI/GR (TXO)
     This transaction/event key is only relevant to Brazil (nota fiscal).
     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.
     Unplanned delivery costs (UPF)
     Unplanned delivery costs are delivery costs (incidental procurement costs) that were not planned in a purchase order (e.g. freight, customs duty). In the SAP posting transaction in Logistics Invoice Verification, instead of distributing these unplanned delivery costs among all invoice items as hitherto, you have the option of posting them to a special account. A separate tax code can be used for this account.
     Input tax, Purchasing (VST)
     Transaction/event key for tax account determination within the "subsequent settlement" facility for debit-side settlement types. The key is needed in the settlement schema for tax conditions.
     Inflation posting (WGB)
     Transaction/event key that posts inflation postings to a different account, within the handling of inflation process for the period-end closing.
     Goods issue, revaluation (inflation) (WGI)
     This transaction/event key is used if already-posted goods issues have to be revaluated following the determination of a new market price within the framework of inflation handling.
     Goods receipt, revaluation (inflation) (WGR)
     This transaction/event key is used if already-effected transfer postings have to be revaluated following the determination of a new market price within the framework of inflation handling. This transaction is used for the receiving plant, whereas transaction WGI (goods receipt, revaluation (inflation)) is used for the plant at which the goods are issued.
     WIP from Price Differences (Internal Activity) (WPA)
     When you use the WIP revaluation of the material ledger, the price variances from the actual price calculation that are to be assigned to the WIP stock, an activity type or a business process are posted to the WIP account for activities.
     WIP from Price Differences (Material) (WPM)
     When you use the WIP revaluation of the material ledger, the price and exchange rate differences that are to be assigned to the WIP stock of a material are posted to the WIP account for material.
     GR/IR clearing (WRX)
     Postings to the GR/IR clearing account occur in the case of goods and invoice receipts against purchase orders. For more on the GR/IR clearing account, refer to the SAP Library (documentation MM Material Valuation).
     Caution
     You must set the Balances in local currency only indicator for the GR/IR clearing account  to enable the open items to be cleared. For more on this topic, see the field documentation.
     GR/IR clearing for material ledger (WRY)
     This transaction/event key is not used from Release 4.0 onwards.
     Prior to 4.0, it was used for postings to the GR/IR clearing account if the material ledger was active. As of Release 4.0, the transaction is no longer necessary, since postings to the GR/IR account in parallel currencies are possible.
     Customers who used the transaction WRY prior to Release 4.0 must make a transfer posting from the WRY account to the WRX account in order to ensure that the final balance on the WRY account is zero.
Thanks,
Rau

OBYC VNG, INV, COC as cost elements

Hi,
I have doubts about accounts assigned in OBYC to VNG (scrapping), INV (Inventarization), COC (material ledger - other consumption variances). Should these accounts be normally created as cost elements in controlling?
Regards,
Karol

Hi,
In OBYC the Transaction event Keys VNG, INV, COC Shoulg be created as cost element. As this keys are related to costing of raw material and inventory Valuation.
Regards,
Sreekanth

/SAPMP/COCA cannot be executed

Hi,
I have an ECC 6.0 System with DIMP activated.
However, for LPP (Long Products Planning) when I try to execute /SAPMP/COCA, it says tcode cannot be executed.
Nor does the relevant "Basic setting for Mill .." node appear in SPRO.
Pls. help.
Thanks,

Hello,
I don't think this is the correct place to ask this question, since here is the forum of SCM(APO) system, while the transaction code you're asking for seems belong to for IS-MP-CA ... Sorry I don't know which forum it belong to
A little hint: If you want to run a transaction code starts from '/', you'll need to add '/n' before it. So just try to input /n/sapmp/coca and run. Good luck~
Best Regards,
Ada

Business transaction key in account determination..?

Hi all
Can anybody explain me in simple form form, what is business transaction key in account determination , for eg, GBB,BSA,BSX,PRD,VBR,.WRX....etc (Approximately 60 transaction keys in std SAP)
If i want to do configuration the for new client, what are all the business transaction key,,, How the configuration wil happen..?
Pls giv me expaination,
Reply will be rewardable..
Thanks
sap-mm

Hi MM,
Please Search in SDN threads solution is given already in lot of threads.
Go to SAP Library
SPRO> Help> SAP Library
Or go to SPRO> IMG> MM>Valuation and Account Assignment>Account determination> Account det without wizard> configure Automatic postings
Click on IMG ACTIVITY DOCUMENTATION
These transactions are important for Accounts.
Postings are made to G/L accounts automatically in the case of Invoice Verification and Inventory Management transactions relevant to Financial and Cost Accounting.
Example:
Posting lines are created in the following accounts in the case of a goods issue for a cost center:
Stock account
Consumption account
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.
Provisions for subsequent (end-of-period rebate) settlement (BO1)
If you use the "subsequent settlement" function with regard to conditions (e.g. for period-end volume-based rebates), provisions for accrued income are set up when goods receipts are recorded against purchase orders if this is defined for the condition type.
Income from subsequent settlement (BO2)
The rebate income generated in the course of "subsequent settlement" (end-of-period rebate settlement) is posted via this transaction.
Income from subsequent settlement after actual settlement (BO3)
If a goods receipt occurs after settlement accounting has been effected for a rebate arrangement, no further provisions for accrued rebate income can be managed by the "subsequent settlement" facility. No postings should be made to the account normally used for such provisions. As an alternative, you can use this transaction to post provisions for accrued rebate income to a separate account in cases such as the one described.
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.
Revaluation of other consumption (COC)
This transaction/event key is required for the revaluation of consumption in Actual Costing/Material Ledger.
Revaluation of consumption valuates single-level consumption using the actual prices determined in the Actual Costing/Material Ledger application. This revaluation can either take place in the account where the original postings were made, or in a header account.
The header account is determined using the transaction/event key COC.
Del credere (DEL)
Transaction/event key for the payment/invoice list documents in Purchasing. The account key is needed in the calculation schema for payment/settlement processing to determine the associated revenue accounts.
Small differences, Materials Management (DIF)
This transaction is used in Invoice Verification if you define a tolerance for minor differences and the balance of an invoice does not exceed the tolerance.
Purchase account(EIN), purchase offsetting account (EKG), freight purchase account (FRE)
These transactions are used only if Purchase Account Management is active in the company code.
Note
Due to special legal requirements, this function was developed specially for certain countries (Belgium, Spain, Portugal, France, Italy, and Finland).
Before you use this function, check whether you need to use it in your country.
Freight clearing (FR1), provision for freight charges (FR2), customs duty clearing (FR3), provision for customs duty (FR4)
These transactions are used to post delivery costs (incidental procurement costs) in the case of goods receipts against purchase orders and incoming invoices. Which transaction is used for which delivery costs depends on the condition types defined in the purchase order.
You can also enter your own transactions for delivery costs in condition types.
External service (FRL)
The transaction is used for goods and invoice receipts in connection with 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.
External service, delivery costs (FRN)
This transaction is used for delivery costs (incidental costs of procurement) in connection with 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.
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:
Purchase order with account assignment (KBS)
You cannot assign this transaction/event key to an account. It means that the account assignment is adopted from the purchase order and is used for the purpose of determining the posting keys for the goods receipt.
Exchange Rate Differences Materials Management(AVR) (KDG)
When you carry out a revaluation of single-level consumption in the material ledger for an alternative valuation run, the exchange rate difference accounts of the materials are credited with the exchange rate differences that are to be assigned to the consumption.
Exchange rate differences in the case of open items (KDM)
Exchange rate differences in the case of open items arise when an invoice relating to a purchase order is posted with a different exchange rate to that of the goods receipt and the material cannot be debited or credited due to standard price control or stock undercoverage/shortage.
Differences due to exchange rate rounding, Materials Management (KDR)
An exchange rate rounding difference can arise in the case of an invoice made out in a foreign currency. If a difference arises when the posting lines are translated into local currency (as a result of rounding), the system automatically generates a posting line for this rounding difference.
Exchange Rate Differences from Lower Levels (KDV)
In multi-level periodic settlement in the material ledger, some of the exchange rate differences that have been posted during the period in respect of the raw materials, semifinished products and cost centers performing the activity used in the manufacture of a semifinished or finished product are debited or credited to that semifinished or finished product.
Consignment liabilities (KON)
Consignment liabilities arise in the case of withdrawals from consignment stock or from a pipeline or when consignment stock is transferred to own stock.
Depending on the settings for the posting rules for the transaction/event key KON, it is possible to work with or without account modification. If you work with account modification, the following modifications are available in the standard system:
None for consignment liabilities
PIP for pipeline liabilities
Offsetting entry for price differences in cost object hierarchies (KTR)
The contra entry for price difference postings (transaction PRK) arising through settlement via material account determination is carried out with transaction KTR.
Accruals and deferrals account (material ledger) (LKW)
If the process of material price determination in the material ledger is not accompanied by revaluation of closing stock, the price and exchange rate differences that should actually be applied to the stock value are contra-posted to accounts with the transaction/event key LKW.
If, on the other hand, price determination in the material ledger is accompanied by revaluation of the closing stock, the price and exchange rate differences are posted to the stock account (i.e. the stock is revalued).
Price Difference from Exploded WIP (Lar.) (PRA)
If you use the WIP revaluation of the material ledger, the price variances of the exploded WIP stock of an activity type or a business process are posted to the price differences account with transaction/event key PRA.
Differences (AVR Price) (PRC)
In the alternative valuation run in the material ledger, some of the variances that accrue interest in the cost centers, are transfer posted to the semifinished or finished product.
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)
Price Differences (Material Ledger, AVR) (PRG)
When you carry out a revaluation of single-level consumption in the material ledger during the alternative valuation run, the price difference accounts of the materials are credited with the price differences that are to be assigned to the consumption.
Price differences in cost object hierarchies (PRK)
In cost object hierarchies, price differences occur both for the assigned materials with standard price and for the accounts of the cost object hierarchy. In the course of settlement for cost object hierarchies after settlement via material account determination, the price differences are posted via the transaction PRK.
Price Difference from Exploded WIP (Mat.) (PRM)
If you use the WIP revaluation of the material ledger, the price and exchange rate differences of the exploded WIP stock of a material are posted to the price difference account with transaction/event key PRM.
Price differences, product cost collector (PRP)
During settlement accounting with regard to a product cost collector in repetitive manufacturing, price differences are posted with the transaction PRP in the case of the valuated sales order stock.
This transaction is currently used in the following instances only:
Production cost collector in Release 4.0
Product cost collector in IS Automotive Release 2.0 (product cost collector in connection with APO)
Offsetting entry: price differences, product cost collector (PRQ)
The offsetting (contra) entry to price difference postings (transaction PRP) in the course of settlement accounting with respect to a product cost collector in repetitive manufacturing in the case of the valuated sales order stock is carried out via transaction PRQ.
This transaction is currently used in the following instances only:
Production cost collector in Release 4.0
Product cost collector in IS Automotive Release 2.0 (product cost collector in connection with APO)
Price Differences from Lower Levels (PRV)
In multi-level periodic settlement in the material ledger, some of the price differences posted during the period in respect of the raw materials, semifinished products, and cost centers performing the activity used in a semifinished or finished product, are transfer posted to that semifinished or finished product.
Price differences for material ledger (PRY)
In the course of settlement in the material ledger, price differences from the material ledger are posted with the transaction PRY.
Expense and revenue from revaluation (retroactive pricing, RAP)
This transaction/event key is used in Invoice Verification within the framework of the revaluation of goods and services supplied for which settlement has already taken place. Any difference amounts determined are posted to the accounts assigned to the transaction/event key RAP (retroactive pricing) as expense or revenue.
At the time of the revaluation, the amounts determined or portions thereof) are posted neither to material stock accounts nor to price difference accounts. The full amount is always posted to the "Expense from Revaluation" or "Revenue from Revaluation" account. The offsetting (contra) entry is made to the relevant vendor account.
Invoice reductions in Logistics Invoice Verification (RKA)
This transaction/event key is used in Logistics Invoice Verification for the interim posting of price differences in the case of invoice reductions.
If a vendor invoice is reduced, two accounting documents are automatically created for the invoice document. With the first accounting document, the amount invoiced is posted in the vendor line. An additional line is generated on the invoice reduction account to partially offset this amount. With the second accounting document, the invoice reduction is posted in the form of a credit memo from the vendor. The offsetting entry to the vendor line is the invoice reduction account. Hence the invoice reduction account is always balanced off by two accounting documents within one transaction.
Provision for delivery costs (RUE)
Provisions are created for accrued delivery costs if a condition type for provisions is entered in the purchase order. They must be cleared manually at the time of invoice verification.
Taxes in case of transfer posting GI/GR (TXO)
This transaction/event key is only relevant to Brazil (nota fiscal).
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.
Unplanned delivery costs (UPF)
Unplanned delivery costs are delivery costs (incidental procurement costs) that were not planned in a purchase order (e.g. freight, customs duty). In the SAP posting transaction in Logistics Invoice Verification, instead of distributing these unplanned delivery costs among all invoice items as hitherto, you have the option of posting them to a special account. A separate tax code can be used for this account.
Input tax, Purchasing (VST)
Transaction/event key for tax account determination within the "subsequent settlement" facility for debit-side settlement types. The key is needed in the settlement schema for tax conditions.
Inflation posting (WGB)
Transaction/event key that posts inflation postings to a different account, within the handling of inflation process for the period-end closing.
Goods issue, revaluation (inflation) (WGI)
This transaction/event key is used if already-posted goods issues have to be revaluated following the determination of a new market price within the framework of inflation handling.
Goods receipt, revaluation (inflation) (WGR)
This transaction/event key is used if already-effected transfer postings have to be revaluated following the determination of a new market price within the framework of inflation handling. This transaction is used for the receiving plant, whereas transaction WGI (goods receipt, revaluation (inflation)) is used for the plant at which the goods are issued.
WIP from Price Differences (Internal Activity) (WPA)
When you use the WIP revaluation of the material ledger, the price variances from the actual price calculation that are to be assigned to the WIP stock, an activity type or a business process are posted to the WIP account for activities.
WIP from Price Differences (Material) (WPM)
When you use the WIP revaluation of the material ledger, the price and exchange rate differences that are to be assigned to the WIP stock of a material are posted to the WIP account for material.
GR/IR clearing (WRX)
Postings to the GR/IR clearing account occur in the case of goods and invoice receipts against purchase orders. For more on the GR/IR clearing account, refer to the SAP Library (documentation MM Material Valuation).
Caution
You must set the Balances in local currency only indicator for the GR/IR clearing account to enable the open items to be cleared. For more on this topic, see the field documentation.
GR/IR clearing for material ledger (WRY)
This transaction/event key is not used from Release 4.0 onwards.
Prior to 4.0, it was used for postings to the GR/IR clearing account if the material ledger was active. As of Release 4.0, the transaction is no longer necessary, since postings to the GR/IR account in parallel currencies are possible.
Reg,
Ashok
assign points if useful.

COPC - CKMLCP Transaction

When I executed CKMLCP transaction, some registers of the table MLCD doesn't paid on the account 69 (Cost of sales)
This happens when two register of the table MLCD have the same ''Cost Estimate Number for Cost Est. w/o Qty Structure''. Only one register paid on the account 69.
Is this situation correct? or both register would paid on the account 69 when the CKMLCP transaction is executed.
Thanks in advance.
José Luis

Go to OBYC/COC/Chart of accounts/Valuation class and enter GL accounts
Revaluation of other consumption (COC)
This transaction/event key is required for the revaluation of consumption in Actual Costing/Material Ledger.
Revaluation of consumption valuates single-level consumption using the actual prices determined in the Actual Costing/Material Ledger
application. This revaluation can either take place in the account where the original postings were made, or in a header account.
The header account is determined using the transaction/event key COC.

Error while comitting a transaction in oSB. The following is the error stack

Error while comitting a transaction in OSB. The following is the error stack
<Apr 20, 2015 12:00:15 AM MDT> <Error> <EJB> <BEA-010026> <Exception occurred during commit of transaction Xid=BEA1-1AE41F1CAE45F2B146FD(296700848),Status=Rolled back. [Reason=Unknown],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=2,seconds left=120,XAServerResourceInfo[WLStore_SOA_PRDKS_DOMAIN_FileStore_SOA_MS2]=(ServerResourceInfo[WLStore_SOA_PRDKS_DOMAIN_FileStore_SOA_MS2]=(state=new,assigned=none),xar=null,re-Registered = false),XAServerResourceInfo[WLStore_OSB_PRDKS_DOMAIN_FileStore_auto_1]=(ServerResourceInfo[WLStore_OSB_PRDKS_DOMAIN_FileStore_auto_1]=(state=rolledback,assigned=OSB_MS1),xar=WLStore_OSB_PRDKS_DOMAIN_FileStore_auto_11603460297,re-Registered = false),XAServerResourceInfo[weblogic.jdbc.jta.DataSource]=(ServerResourceInfo[weblogic.jdbc.jta.DataSource]=(state=ended,assigned=none),xar=CMSDS,re-Registered = false),SCInfo[OSB_PRDKS_DOMAIN+OSB_MS1]=(state=rolledback),SCInfo[SOA_PRDKS_DOMAIN+SOA_MS2]=(state=pre-prepared),properties=({}),local properties=({weblogic.jdbc.jta.CMSDS=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=OSB_MS1+soaprd-vip-osb-ms1.cos.is.keysight.com:8001+OSB_PRDKS_DOMAIN+t3+, XAResources={eis/wls/Queue, WEDB_EVEREST_OSB_PRDKS_DOMAIN, XREFDS_OSB_PRDKS_DOMAIN, eis/activemq/Queue, CustomSchemaDS_OSB_PRDKS_DOMAIN, MobileApps_CIA_DS1_OSB_PRDKS_DOMAIN, eis/tibjmsDirect/Queue, eis/jbossmq/Queue, eis/Apps/Apps, MobileApps_AOS_MDS_OSB_PRDKS_DOMAIN, MobileApps_AOS_DRDS_OSB_PRDKS_DOMAIN, WSATGatewayRM_OSB_MS1_OSB_PRDKS_DOMAIN, eis/webspheremq/Queue, eis/AQ/aqSample, SBLPROD_OSB_PRDKS_DOMAIN, wlsbjmsrpDataSource_OSB_PRDKS_DOMAIN, eis/aqjms/Queue, CMSDS_OSB_PRDKS_DOMAIN, WLStore_OSB_PRDKS_DOMAIN_WseeFileStore_auto_1, FAP_OSB_PRDKS_DOMAIN, eis/sunmq/Queue, eis/pramati/Queue, FMWAPPDS_OSB_PRDKS_DOMAIN, weblogic.jdbc.jta.DataSource, GSDC_OSB_PRDKS_DOMAIN, eis/tibjms/Topic, eis/fioranomq/Topic, WLStore_OSB_PRDKS_DOMAIN_FileStore_MS1, PresidioOracleAppsDS_OSB_PRDKS_DOMAIN, GSDCDS_OSB_PRDKS_DOMAIN, eis/aqjms/Topic, CustOutDS_OSB_PRDKS_DOMAIN, OFMW/Logging/BAM, MobileAppsDS_OSB_PRDKS_DOMAIN, FIDDS_OSB_PRDKS_DOMAIN, WLStore_OSB_PRDKS_DOMAIN__WLS_OSB_MS1, HRMSDS_OSB_PRDKS_DOMAIN, WEDB_OSB_PRDKS_DOMAIN, OracleAppsDS_OSB_PRDKS_DOMAIN, eis/wls/Topic, eis/tibjms/Queue, eis/tibjmsDirect/Topic, IntrastatDS_OSB_PRDKS_DOMAIN, MobileApps_AOS_COSDS_OSB_PRDKS_DOMAIN, MobileApps_CIA_DS2_OSB_PRDKS_DOMAIN, EVEREST_WEDB_OSB_PRDKS_DOMAIN, WLStore_OSB_PRDKS_DOMAIN_FileStore_auto_1, Everest_OSB_PRDKS_DOMAIN},NonXAResources={})],CoordinatorURL=SOA_MS2+soaprd-vip-soa-ms2.cos.is.keysight.com:8002+SOA_PRDKS_DOMAIN+t3+): javax.transaction.SystemException: Lost connection to server while commit was in progress, ignoring because initiating server is not coordinating server. Remote Exception received=weblogic.rjvm.PeerGoneException: ; nested exception is:
 java.rmi.UnmarshalException: Incoming message header or abbreviation processing failed ; nested exception is:
 java.io.InvalidClassException: oracle.jdbc.xa.OracleXAException; local class incompatible: stream classdesc serialVersionUID = -2542408691177300269, local class serialVersionUID = -4551795881821760665
 at weblogic.transaction.internal.TransactionImpl.commit(TransactionImpl.java:376)
 at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:237)
 at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:224)
 at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:552)
 at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:423)
 at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:325)
 at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4659)
 at weblogic.jms.client.JMSSession.execute(JMSSession.java:4345)
 at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3821)
 at weblogic.jms.client.JMSSession.access$000(JMSSession.java:115)
 at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5170)
 at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

Hi,
Have you tried Cancelling the release before adding the version?
Select the active version of the IDOC Segment and cancel its release first. Only then you will be able to add a version.
Please let me know if it worked!
Vijay

Doubt in fbl1n transaction

hi i have a doubt....
in fbl1n transaction, there are open items and cleared items.
in it the cleared items for certain document types such as invoice etc is not present in the open item table (bsik)
however the cleared items for document types such as general voucher its present in the open items table (bsik)
is this possible as all cleared item entries shld b present in the open item table with an indicator set for cleared or not...
plz exlain!

Hi
There are 2 tables(open and Closed Items) in FI for Account Payables and Account Receivables and GL accounts
1.Account payables: BSIK is Open Items and BSAK is Closed items
2.Account Receivables; BSID and BSAD for OPEN and closed items
3/GL accounts : BSIS and BSAS for Open and Closed Items
Reward points for useful Answers
Regards
Anji

Busniees Transaction COC

Similar Messages

Maybe you are looking for