Event key issue

hi
Account 1211019100 for trans./event key BSX is a K control account ??
it means???
could you explain me??
reagerds
ss

Hi,
As for my understanding about your question,
The event key BSX is related to inventory posting, here "K" indicates vendor account. Are you trying to alocate this event key to some customer account or to some SD related transactions?
Thanks,
Regards,
Ramnath.

Similar Messages

Incorreect event-key in oracle.apps.inv.lotCreate Event PL/SQL Rule Functio

Hi,
I have created event subscription as PL/SQL function for oracle.apps.inv.lotCreate Event.
In this PL/SQL function, i am calling "getEventKey" method on WF_EVENT_T object obtained.
However, value returned by this "getEventKey" method is incorrect. According to Oracle Inventory User Guide, event-key should be
Organization_id-Item_id-Lot_number. However i am getting some six digit number which is neither Organization_id nor Item_id nor Lot_number.
I am using Oracle E-Business suite Release 12.
Please let me know if anyone has faced similar problems? what was cause of such problem?
Any pointers regarding the issue will be highly appreciated.
Let me know if you require more information.
Thanks,
Rohit

Hi Steve,
The test subscription is raising from the workflow administrator responsiibility but when I update the item attribute controls then the subscription is not raising and checked with the forms trace, there is no event is recorded in the trace. I am using 11.5.10 cu 2 version and suspecting still some setting might be missing for the inventory events.
I wrote the following code for my initial testing to test the event subscription raising on the item update.
CREATE OR REPLACE PACKAGE BODY APPS.schl_event_item_update_elt
AS
FUNCTION schl_item_attrib_update (p_subscription_guid IN raw,
p_event IN OUT wf_event_t
RETURN VARCHAR2
IS
l_key VARCHAR2 (240);
l_key_stat VARCHAR2 (50);
l_status_rec VARCHAR2 (50);
l_org_id VARCHAR2 (240);
BEGIN
l_key := p_event.geteventkey ();
INSERT INTO schl.schl_item_attrib_update
VALUES (l_key);
RETURN 'SUCCESS';
EXCEPTION
WHEN NO_DATA_FOUND
THEN
INSERT INTO schl.schl_item_attrib_update
VALUES ('error');
END;
END;
I would highly appreciate your thoghts on this.
Thanks,
Srini C

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

Acct X for trans./event key BSX is a K control account.

Dear Experts:
I am not so familiar with FI and one question need your help:
When I was trying to post a goods receipt against one purchase order I created earlier, I got an error message: "Account 199999 for trans./event key BSX is a K control account'
For account 199999, the account group is Recon. account and acct type is Vendors.
Can anybody let me know the solution to this issue? Thank you all in advance!
Best Regards!
Tim

Hi Eli:
Thanks for your reply. But if I delete the account in OBYC, I will get another error message: "Account determination for entry TDCC BSX 0001 ___ ZZXX not possible". If I maintain the entry: "0001 ZZXX 19999" in BSX in OBYC, I will get the error above.
Do you know how to resolve that?
Thanks~
Tim

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

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

Creation of NewTransaction/Event Key in OBYC - FR5

Hi
wish to create a new Transaction - similar to FR1, in OBYC
I have created new trasanction event key @ IMG - MM - Purchasing - Conditions - Define price determination process - Define transaction/event keys
Then in OBYC assignd the G/L account as per requirement
Have i missed any steps?

Hi,
Have created a new condition type FR5 by copying the similar condition FR1(or whatever) in M/06,and have u added the condition type to ur pricing procedure.
if no then do above things and if yes then your config is fine....
if else your facing any issues, reply back with exact issue.
hope it halpes you.
Thanks
Abdul

Transaction key / event key in account determination??

hii
I want to know what is transaction key and event key in account determination??
Thanks

HI,
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. Account grouping (only for offsetting entries, consignment liabilities, and price differences) Since the posting transaction "Offsetting entry for inventory posting" is used for different transactions (for example, goods issue, scrapping, physical inventory), which are assigned to different accounts (for example, consumption account, scrapping, expense/income from inventory differences), it is necessary to divide the posting transaction according to a further key: account grouping code. An account grouping is assigned to each movement type in inventory management which uses the posting transaction "Offsetting entry for inventory posting". Under the posting transaction "Offsetting entry for inventory posting", you must assign G/L accounts for every account grouping, that is, assign G/L accounts. If you wish to post price differences to different price difference accounts in the case of goods receipts for purchase orders, goods receipts for orders, or other movements, you can define different account grouping codes for the transaction key. Using the account grouping, you can also have different accounts for consignment liabilities and pipeline liabilities. Valuation class of material or (in case of split valuation) the valuation type The valuation class allows you to define automatic account determination that is dependent on the material. for example: you post a goods receipt of a raw material to a different stock account than if the goods receipt were for trading goods, even though the user enters the same transaction for both materials. You can achieve this by assigning different valuation classes to the materials and by assigning different G/L accounts to the posting transaction for every valuation class. If you do not want to differentiate according to valuation classes you do not have to maintain a valuation class for a transaction.
Regards
KK

Transfer Event Key

What do u mean by Transfer Event Key ? and where it was used ?

Hi,
If you are looking for Transaction Event Key. please go through th below.
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.
<b>( In Simple Wards, Each movement type is attached to a Value string which consists of set of transactions event keys, transaction event keys are attached to GL accounts in Configuration of automatic postings, When ever we run any transaction in inventory management system will identify certain movement type, already the movement type is attached to Value string which conists of TE keys, those are linked to GL accounts for postings)
Refer tables T156S & T156W for movement type and Value string ,Value string and TE keys</b>
The following list shows the individual transactions with examples of how they are used. The transaction/event key is specified in brackets.
     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:
o     In inventory management in the case of goods receipts to own stock and goods issues from own stock
o     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
o     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:
o     A stock account is not used for any transaction other than BSX
o     Postings are not made to the account manually
o     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:
o     AUA: for order settlement
o     AUF: for goods receipts for orders (without account assignment)
and for order settlement if AUA is not maintained
o     AUI: Subsequent adjustment of actual price from cost center directly
to material (with account assignment)
o     BSA: for initial entry of stock balances
o     INV: for expenditure/income from inventory differences
o     VAX: for goods issues for sales orders without
account assignment object (the account is not a cost element)
o     VAY: for goods issues for sales orders with
account assignment object (account is a cost element)
o     VBO: for consumption from stock of material provided to vendor
o     VBR: for internal goods issues (for example, for cost center)
o     VKA: for sales order account assignment
(for example, for individual purchase order)
o     VKP: for project account assignment (for example, for individual PO)
o     VNG: for scrapping/destruction
o     VQP: for sample withdrawals without account assignment
o     VQY: for sample withdrawals with account assignment
o     ZOB: for goods receipts without purchase orders (mvt type 501)
o     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:
o     None for consignment liabilities
o     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:
o     None for goods and invoice receipts against purchase orders
o     PRF for goods receipts against production orders and
order settlement
o     PRA for goods issues and other movements
o     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 & Regards,
Sridhar

T event key GBB

Hi Gurus,
I am getting confused with the use of transaction event key GBB. Is it not supposed to be used for account updates during the Goods issue or consumptions? In my clients system when we create a PO for a service with account assignment either to a work order or an equipment, the GR calls the updates in the GBB which means the updates are made to the accounts given in the GBB. Can any one tell me and explain in details why is this happening?
I hope I was able to explain the question properly else I will try to tell you in more clear SAP language.
thanks in advance
Anoop

Hi,
The use of transaction event key GBB, in case of PO for a service with account assignment being used for account determination without material master and here G/Lu2019s are assigned with material group and material group assigned to valaution class in OMQW t.code.
You can check all assignments in following t.codes
OMQW,OME9, OMGO & OBYC
Chcek the link for GBB used in OBYC t.code for service PO/without a material master PO with account assignment :
http://www.bluemarlinsys.com/ns/0603-03.asp
Regards,
Biju K

Tecra M10 - Stuck CTRL key issue -- perhaps to do with BIOS?

Hello and thanks for reading.
I recently switched my Tecra M10 to Windows 7 (from XP) and it soon developed the dreaded "stuck CTRL key" issue. This causes the keyboard to behave as if the CTRL key is permanently depressed. Sometimes hitting a combination of keys, or bringing up the onscreen keyboard, temporarily solves the issue, but then it returns.
It seems to be an issue many people have, with no simple solution. I've looked at every thread about it I can find, and tried many things to do with drivers etc. without any success.
So firstly, if anyone knows a remedy that works for this particular machine, I would be very grateful to learn it!
Then, there are two things I've not yet done: update BIOS and disable pinch zoom.
I was looking at the following BIOS update:
http://www.toshiba-asia.com/sg/support/drivers/details/25244
... which is version 3.00 and seems to be most recent. My own version is 1.90.
However version 3.00 is labelled "For PTMB0* ONLY". I don't know what this means or whether it applies to me. Can anyone help? Should I install this BIOS?
For the pinch zoom, I've been told that disabling it does sometimes cure the CTRL problem -- but I can't find any pinch zoom facility on the M10. I suspect it simply doesn't have one. Is that right?
Many thanks for any help you can give.

Hi
> I was looking at the following BIOS update. which is version 3.00 and seems to be most recent. My own version is 1.90.
There are different Tecra M10 models on the market.
Check the labels at the bottom of the unit. There you should find some numbers like for example PTMB0E-01K00LGR
The first 6 characters are important: for example PTMB0E
I assume your notebook belongs to European series.
In such case you should check the Toshiba EU driver page for possible BIOS update.
http://www.toshiba.eu/innovation/download_drivers_bios.jsp
However, on Toshiba EU driver page you will find also the BIOS v3.0 for all European Tecra M10 units.
Anyway, back to the CTRL button issue: guess what, you should connect an external USB keyboard and should check how the CTRL button acts.
In case the USB keyboard would work properly, the CTRL button of internal keyboard is affected and you will need to replace the internal keyboard.
PS: it could be possible that the option "sticky keys" has been enabled. To disable this function, you have to press SHIFT button 5 times in the row.

Incorreect event-key in oracle.apps.inv.lotCreate Event subscription

Hi,
I have created event subscription as PL/SQL function for oracle.apps.inv.lotCreate Event.
In this PL/SQL function, i am calling "getEventKey" method on WF_EVENT_T object obtained.
However, value returned by this "getEventKey" method is incorrect. According to Oracle Inventory User Guide, event-key should be
Organization_id-Item_id-Lot_number. However i am getting some six digit number which is neither Organization_id nor Item_id nor Lot_number.
I am using Oracle E-Business suite Release 12.
Please let me know if anyone has faced similar problems? what was cause of such problem?
Let me know if you require more information.
Thanks,
Rohit

Hi Steve,
The test subscription is raising from the workflow administrator responsiibility but when I update the item attribute controls then the subscription is not raising and checked with the forms trace, there is no event is recorded in the trace. I am using 11.5.10 cu 2 version and suspecting still some setting might be missing for the inventory events.
I wrote the following code for my initial testing to test the event subscription raising on the item update.
CREATE OR REPLACE PACKAGE BODY APPS.schl_event_item_update_elt
AS
FUNCTION schl_item_attrib_update (p_subscription_guid IN raw,
p_event IN OUT wf_event_t
RETURN VARCHAR2
IS
l_key VARCHAR2 (240);
l_key_stat VARCHAR2 (50);
l_status_rec VARCHAR2 (50);
l_org_id VARCHAR2 (240);
BEGIN
l_key := p_event.geteventkey ();
INSERT INTO schl.schl_item_attrib_update
VALUES (l_key);
RETURN 'SUCCESS';
EXCEPTION
WHEN NO_DATA_FOUND
THEN
INSERT INTO schl.schl_item_attrib_update
VALUES ('error');
END;
END;
I would highly appreciate your thoghts on this.
Thanks,
Srini C

OMWB transaction key Issue

Dear All,
As per our customer's requirements we have created a new transaction/event key & assigned the same in existing Cal.Schema. The G/L A/C for the new trans key is also defined in OBYC.
After all the these when we Checked in OMWB transaction - G/L accounts tab then both transaction key as well as the G/L which we assigned to the new transaction is not displayed..
So can anyone provide some inputs on why the system is not displaying the newly created G/L & transaction key in OMWB - G/L Accounts tab ?
Thanks in advance & Have a Nice Day!
Regards,

Hi Kishore,
Thanks a lot for the reply.
As you suggested I have checked in T030 table & I can find a entry there with values for Chart of A/Cs, Trans Key & G/L A/C. (Since in OBYC I have specified my G/L A/C for trans key with ref to Posting key only)
So the fields - Val grouping code, valuation class & Acct modifier are blank for the above entry.
Now even if there is an entry in the above table the transaction key & G/L A/C is not displayed in OMWB - G/L A/C tab.
Hope its clear.
Awaiting your reply..
Regards,

Windows 8 Key Issue

Here's my problem. Windows 8 came preinstalled on my computer; however, I accidently deleted the Windows 8 key from the bios and now Windows keeps asking me to enter the correct key. Since there is no longer a sticker with the key included with the computer I have no way of finding the key. Does HP keep a record of the keys tagged to the serial number? Or am I just out of luck?
I called HP Support about this and they told me to get the key off the CDs which were included with the computer. When I told him there were no CDs, he said I had bought a used computer mascarading as new because all of their computers ship with Windows CDs. When I disputed this he said that Microsoft could solve the issue for me. Microsoft said that HP could solve it. Can anyone help me? I'd rather not spend money on buying Windows 8
Thanks in advance,
Mike
This question was solved.
View Solution.

HP does not retain records of the keys issued . HP also does not ship Windows CD's with the computers unless they were specifically ordered. If you have somehow deleted the key then you are out of luck, sorry.
Please mark my post as SOLVED if it has resolved your problem. It helps others with similar situations.

T400 stuck key issue

I bought my T400 2764-CTO in last December, and started using it on mini dock without any problem. Until recently, it starts to show stuck key issue randomly (not always failure) both at boot up or under Windows Vista.
ERROR
0210 Stuck Key FF
Press <F1> to SetUp
Note: the stuck key keeps changing, sometimes 13, sometimes 1F, sometimes other key.
I opened the laptop, and checked the connection of the keyboard but couldn't locate any problem there. Can this be a keyboard issue? Or even a motherboard issue?
Can Lenovo swap a new keyboard for me? If so, what do I need to do then?
Thanks!
Best Regards

You can call Lenovo service, and log a service call, they will make the necessary arrangements. If you are not confident with bios update then please don't do it youself, and let the warranty department do it for you, as any mistakes can make your laptop useless and you will be paying couple hundreds of euros to get the motherboard replaced.
Regards,
Jin Li
May this year, be the year of 'DO'!
I am a volunteer, and not a paid staff of Lenovo or Microsoft

Event key issue

Similar Messages

Maybe you are looking for