11.5.10: RETROACTIVE PRICING이 WORKFLOW를 통해 수행되지 않을 경우 처리 방법

제품 : MFG_PO
작성날짜 : 2006-05-30
11.5.10: RETROACTIVE PRICING이 WORKFLOW를 통해 수행되지 않을 경우 처리 방법
===========================================================
PURPOSE
11.5.10: Retroactive Pricing이 workflow form을 통해 수행되지 않을 경우
처리 방법을 기술하고자 합니다.
Problem Description
Steps:
1. Create a Blanket PO
2. Create a release for the blanket
3. Change price on blanket purchase order.
While approving, check the 'Apply price update to existing PO's
and releases' box.
4. Run the workflow Background process for the PO Approval workflow.
The workflow is completed.
5. The price change is not reflected on the release.
6. If the 'Retroactive Price Update of Purchasing Documents' program
is run, the new price is reflected on the release.
CAUSE
=====
workflow background process에 의해 mass_update_release program이 trigger될 때, 정상적으로 값을 가져오지 못하는 문제가 있음.
Workaround
Set the profile option to "ALL Releases" at the site level.
Solution Description
다음과 같은 step으로 수행하시기 바랍니다.
step1. Download and review the readme and pre-requisites for
Patch#4901406
step2. Apply Patch 4901406 in a test environment.
step3. Confirm the following file versions:
POXWPA6B.pls 115.68.11510.6
POXWPA7B.pls 115.38.11510.7
step4. Retest the issue.
step5. If the issue is resolved, please migrate the solution
as appropriate to other environments.
Reference Documents
Bug 4917740 FPJ: RETROACTIVE PRICING DOES NOT WORK WITH WORKFLOW.

Similar Messages

[Q] about AP INVOICE CREATED BY RETROACTIVE PRICING.

Hello
ERP : R11.5.10 CU2
The adjustment invoice created as a result of Retroactive Pricing does not allow 'Force Approval' Action on the invoice.
Thus it cannot be manually approved.
* Steps
1. Retroactive Price Update Concurrent
2. <Create Adjusting Documents in Payables Program> Concurrent
3. Invoice is created.
Invoice Type "PO Price Adjustment"
4. User can validate this invoice, but it cannot be manually approved.
Question]
Is this standard functionality or not?
Can this functionality be changed by setup (or something)?
Thank you
Mihye

Yes. This is the intended functionality. The Apply/Unapply Prepayment Check Box and Force Approval Check Box are greyed out for PO Price Adjustment Document.
Thanks

MM-FI Intergration

Hello SAP Experts,
I am having difficulty understanding what 'General Modification' tab in OBYC means?
I have defined my valuation classes for materials but am finding it difficult to actually assign accounts to transaction keys.
Can someone please explain various material movement types and the accounts affected due to that movement and how 'general modification' comes into picture.
I need it really badly and really urgently.
Thanks,
Elizaa

Thefollowing documentation will help you in understanding the various transactions in OBYC and also in configuring the same:
Configure Automatic Postings
In this step, you enter the system settings for Inventory Management and Invoice Verification transactions for automatic postings to G/L accounts.
You can then check your settings using a simulation function.
Under Further information there is a list of transactions in Materials Management and their definitions.
What are automatic postings?
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
How does the system find the relevant accounts?
When entering the goods movement, the user does not have to enter a G/L account, since the ERP system automatically finds the accounts to which postings are to be made using the following data:
Chart of accounts of the company code
If the user enters a company code or a plant when entering a transaction, the ERP system determines the chart of accounts which is valid for the company code.
You must define the automatic account determination individually for each chart of accounts.
Valuation grouping code of the valuation area
If the automatic account determination within a chart of accounts is to run differently for certain company codes or plants (valuation areas), assign different valuation grouping codes to these valuation areas.
You must define the automatic account determination individually for every valuation grouping code within a chart of accounts. It applies to all valuation areas which are assigned to this valuation grouping code.
If the user enters a company code or a plant when entering a transaction, the system determines the valuation area and the valuation grouping code.
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.
Requirements
Before you maintain automatic postings, you must obtain the following information:
1. Valuation level ( plant or company code)
Establish whether the materials are valuated at plant or at company code level
When valuation is at plant level, the valuation area corresponds to a plant.
When valuation is at company code level, the valuation area corresponds to a company code.
Define valuation level
2. Chart of accounts and valuation grouping code per valuation area
Find out whether the valuation grouping code is active.
Activate split valuation
If it is not active, determine the chart of accounts assigned to each valuation area (via the company code).
If it is active, determine the chart of accounts and the valuation grouping code assigned to each valuation area.
Group valuation areas
You must define a separate account determination process for chart of accounts and each valuation grouping code.
3. Valuation class per material type
If you wish to differentiate the account determination process for specific transactions according to valuation classes, find out which valuation classes are possible for each material type.
Define valuation classes
4. Account grouping for offsetting entries to stock accounts
Under Define account grouping for movement types, determine for which movement types an account grouping is defined for the transaction/event keys GGB (offsetting entry to stock posting), KON (consignment liabilities) and PRD (price differences).
Default settings
G/L account assignments for the charts of accounts INT and the valuation grouping code 0001 are SAP standard.
Activities
1. Create account keys for each chart of accounts and each valuation grouping code for the individual posting transactions. To do so, proceed as follows:
a) Call up the activity Configure Automatic Postings.
The ERP system first checks whether the valuation areas are correctly maintained. If, for example, a plant is not assigned to a company code, a dialog box and an error message appear.
From this box, choose Continue (next entry) to continue the check.
Choose Cancel to end the check.
The configuration menu Automatic postings appears.
b) Choose Goto -> Account assignment.
A list of posting transactions in Materials Management The Account determination indicator shows whether automatic account determination is defined for a transaction.
c) Choose a posting transaction.
A box appears for the first posting transaction. Here you can enter a chart of accounts.
You can enter the following data for each transaction:
Rules for account number assignments
With Goto -> Rules you can enter the factors on which the account number assignments depend:
- debit/credit indicator
- general grouping (= account grouping)
- valuation grouping
- valuation class
Posting keys for the posting lines
Normally you do not have to change the posting keys. If you wish to use new posting keys, you have to define them in the Customizing system of Financial Accounting.
Account number assignments
You must assign G/L accounts for each transaction/event key (except KBS). You can assign these accounts manually or copy them from another chart of accounts via Edit -> Copy.
If you want to differentiate posting transactions (e.g. inventory postings) according to valuation classes, you must make an account assignment for each valuation class.
Using the posting transaction "Offsetting entry for inventory posting", you have to make an account assignment for each account grouping
If the transaction PRD (price differences) is also dependent on the account grouping, you must create three account assignments:
- an account assignment without account grouping
- an account assignment with account grouping PRF
- an account assignment with account grouping PRA
If the transaction KON (consignment and pipeline liabilities) is also dependent on the account grouping, you must create two account assignments:
- an account assignment without account grouping (consignment)
- an account assignment with account grouping (pipeline)
d) Save your settings.
2. Then check your settings with the simulation function.
With the simulation function, you can simulate the following:
Inventory Management transactions
Invoice Verification transactions
When you enter a material or valuation class, the ERP system determines the G/L accounts which are assigned to the corresponding posting transactions. Depending on the configuration, the SAP system checks whether the G/L account exists
In the simulation you can compare the field selection of the movement type with that of the individual accounts and make any corrections.
If you want to print the simulation, choose Simulation -> Report.
To carry out the simulation, proceed as follows:
a) Choose Settings to check the simulation defaults for
- the application area (Invoice Verification or Inventory Management)
- the input mode (material or valuation class)
- account assignment
Instructions
b) Choose Goto -> Simulation.
The screen for entering simulation data appears.
c) Depending on the valuation level, enter a plant or a company code on the screen.
d) When you simulate Inventory Management transactions, goods movements are simulated. The ERP system suggests the first movement type for simulation. If several movements are possible with this movement type, you can select a line.
When you simulate Invoice Verification transactions, a list appears on the screen of the possible transaction types. Select a line.
e) Then choose Goto -> Account assignments.
A list appears of the posting lines which can be created by the selected transaction. For each posting line, the G/L account for the debit posting as well as the G/L account for the credit posting are displayed.
f) From this screen, choose Goto -> Movement+ to get a list of the posting lines for the next movement type or transaction type.
If you work with valuation classes, choose Goto -> Valuation class+ to receive the simulation for the next valuation class. This function is not possible when simulating with material numbers.
Choose Goto -> Check screen layout to compare the movement type with the G/L accounts determined by the system and make any necessary corrections.
Note
The simulation function does NOT obviate the need for a trial posting!
Further notes
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:
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 and GBB, 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 and GBB, 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
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

Interface Programing thru ABAP

Hi Abapers,
I have created LLD for one interface, but do not know how to convert it to actual coding. Please help me out in same. please help me in atleast as much points in which you can.
A) For standard price change:-
A.1) Update the pricing date:-
     VBKD-PRSDT = tomorrows date.
A.2) To update the price:-
Part of standard function SD_BULK_CHANGE:-
[ RV45C = DYNPRO_FIELDS.
CASE FUNCTION.
      WHEN 'MPRF'.
      CLEAR FLAG.
      CLEAR NEW_VBELN.
      CLEAR PREISFINDUNG.
      till endform.
1)     Select line within the new ZPRICE table
Where           VBAK.VBELN = ZPRICE.VBELN (Contract #)
VBAK.POSNR = ZPRICE.POSNR (Item#)
2)     Compare net price (NETPR) for that line within the ZPRICE table to the calculated tomorrows price determined in step 1 above. If price is the same do nothing. If price has changed delete previous entry and make a new entry. If no entry is found in the ZPRICE table for a specific contract and item combination make a new entry. Populate the new entry using the following logic.
     ZPRICE.VBELN = VBAP.VBELN (Contract #)
     ZPRICE.POSNR = VBAP.POSNR (Item #)
     ZPRICE. WAERK = VBAP.WAERK (Document Currency)
     ZPRICE.NETPR = VBAP.NETPR (Net Price)
     ZPRICE.MEINS VBAP.MEINS (Item base unite of measure)
     ZPRICE.DATAB = Tomorrows Date
     ZPRICE.ERDAT = Todays Date
3)     Select price condition records that were created today and have effective dates in the past
Select      KONH.KNUMH (Condition record number)
     KONH.DATAB (Valid-From Date)
Where      KONH.KVEWE = A (Usage = Pricing)
     KONH.KAPPL = V (Application = Sales/Distribution)
KONH.ERDAT = Todays Date (Created on date)
KONH.DATAB < Todays Date (Valid-From Date is in the past)
4)     Select customer menus associated with the retroactive pricing condition record
Select      VBAP.VBELN (Contract #)
     VBAP.POSNR (Item #)
Where     KONV.KNUMH = KONH.KNUMH (Condition record number)
VBAK.KNUMV = KONV.KNUMV (Document condition number)
VBAK.AUART = ZMNU (Document Type)
VBAP.POSNR = KONV.KPOSN (Item #)
5)     Select net price for contract line item within the new ZPRICE table
Select      ZPRICE.NETPR (Net Price)
Where      VBAK.VBELN = ZPRICE.VBELN (Contract #)
VBAK.POSNR = ZPRICE.POSNR (Item#)
Determine and compare the net price of the contract line item for each previous day until the net price no longer equals the net price within the ZPRICE table. When complete, Use Function from which is used step A
6)     Within ZPRICE table change the effective date (ZPRICE.DATAB) to the last day the price equalled ZPRICE.NETPR. In the above example the date would be 8/01/2006 since the price was different on 7/31/2006.
7)     Select all customer menu and item combinations that are associated with each customer pricing contact that have an associated output condition record in table B504 (Customer Pricing Contact PARNR)
Select           B504.PARNR (Contact #)
VBPA.VBELN (Contract #),
VBPA.POSNR (Item #)
Where           VBPA.PARNR = B504.PARNR (Contact #)
          VBPA.PARVW = Z8
          VBAK.AUART = ZMNU
Inner Join      VBAK.VBELN = VBPA.VBELN
Contact #     Contract #     Item #
50000     0040000010     10
50002     0040000010     20
50003     0040000021     10
50005     0040000010     10
50005     0040000021     20
8)     Per pricing contact determine if the price has changed for any contract and item combination assigned to that pricing contact. If price has changed, then trigger price change notification for the pricing contact.
     If at least one of the pricing contacts assigned contract and item combinations within the ZPRICE table has an entry date (ZPRICE.ERDAT) equal to todays date trigger the output for this pricing contact.

hi,
dictionary interfaces: you define your interface with reference to dictionary objects (structures, ansd so on). If your form uses a dictionary interface you can use special types in your interface for texts (smartform or include texts), adresses, graphics, and so on...
if you use an XML interface and create it by your own you can upload a xml file that represents your data file.
XML Interfaces are created by the system if you create your form out of web dynpro abap (online scenario).
To use tables and information out of your application without web dynpro i would recommend you to use ddic interfaces, web dynpro xml.
Norbert

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

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.

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

Automate Process - Excel, and workflow for Pricing

Hi,
We want to automate the process (not necessary in SAP). Currently, the users are creating couple of Excel worksheets with landed cost, fob, duty, insurance etc to come up with Landed cost and calculate the Gross margin for each product. Once this is completed, they get the excel worksheet approve by their manager, Vice president before the pricing condition records are getting created in SAP.
We want to put this Excel Mechanism in some sort of technology where uesr can input the data and calculation can be done. They can save this as draft and revised it before submitting it for approval. On the press of certain button, the workflow should be called so that it goes to appropriate user for their approval and in the last, create the appropriate condition record in the SAP
Any one has implemented this type of mechanism, and if yes, which technology have you used. If not used, can you suggest the best technology to use.
Thanks

Hi,
We want to automate the process (not necessary in SAP). Currently, the users are creating couple of Excel worksheets with landed cost, fob, duty, insurance etc to come up with Landed cost and calculate the Gross margin for each product. Once this is completed, they get the excel worksheet approve by their manager, Vice president before the pricing condition records are getting created in SAP.
We want to put this Excel Mechanism in some sort of technology where uesr can input the data and calculation can be done. They can save this as draft and revised it before submitting it for approval. On the press of certain button, the workflow should be called so that it goes to appropriate user for their approval and in the last, create the appropriate condition record in the SAP
Any one has implemented this type of mechanism, and if yes, which technology have you used. If not used, can you suggest the best technology to use.
Thanks

VK11 - Pricing Condition Workflow

Dear friends ,
I looking for sap workflow for VK11 - Pricing Condition . I have checked in sap for business objects & user exits and i could not able to find any thing.
Can some one suggest me the way out to develop workflow for VK11 ( create / change conditions)
Thanks and Regards,
Vijay

Hi Vijay,
Please check following thread:
Re: Re : Workflow for Pricing Condition Creation ( VK11)
Hope it helps.
Regards,
Akshay
Note: Pls mark helpful answers.

Shared Project Workflow Problem: Hitting a Wall with Markers

Hi there,
Apologies in advance for the long note. We're using Adobe CC to edit and finish commercials and are having a significant issue regarding shared project workflow. First, some context:
We often edit projects remotely. When this happens, assistants and other editors who remain in LA will have access to the media on our SAN while the editor and assistant traveling out of town will have their own copy of the media. I know Adobe Anywhere would solve any issue relating to two identical sets of media in use in different cities, but we're a small shop and the hardware and software expense don't make sense for us at this time. Please do not respond to anything mentioned from here on by stating we should just get Adobe Anywhere. Thanks.
What will regularly happen is that the remote editor and assistant will need work done on the project here in LA while they're in session with the clients. Sometimes this work involves marking up clips with comment markers so the editor can more easily locate a specific moment. Here's where the problem arises.
Unlike FCP and Avid, Premiere handles markers within the clip's metadata. So, if I have two separate projects linking to separate but identical instances of media, one of those media instances gets updated with new markers, there is currently no way to get those markers to the other project without also shuttling the new marked-up media. This is not possible when a remote editor needs dailies marked up in a couple hours and is working across the country or abroad.
But let's assume for the sake of argument that it is possible and we apply this workflow. Let's also assume that in the time it takes the local assistant to mark up the clips for the remote editor, the editor has added a couple markers of his own, which is reasonable and happens all the time. Now when the editor links to the newly marked up clips he's received via shipment, he'll wipe out all the markers he's made on his own since giving the order to mark up the footage. That is a significant inconvenience, especially with clients in the room asking stuff like "can we look at the take where the guy says 'good' instead of 'great'?"
So what happens if we just have repeating sets of media, so that every time the clips markers get updated, the editor actually imports those clips, even though the picture and audio data in those clips is completely redundant to what's already in the project. The issues with this are, as I can see it, 1) increasing the amount complexity within the project so that you'd have to scan many bins of dailies to look for a single marker, 2) increasing by orders of magnitude the amount of storage space needed, 3) even if problems 1 and 2 are handled, if you have to go to finish with multiple versions of a cut, and those versions reference separate instances of the same clip from different bins, Premiere's dupe frame detection will not work and you'll need to spend a lot of extra time locating duplicate clips manually before sending your EDL or XML off to final color grading.
At this point, I think it's necessary to interject something: we're talking about markers here. Why is this such a problem? FCP and Avid have no such issues simply by making markers - even clip markers - part of the project metadata. From what I understand, Adobe has chosen to do things differently because of dynamic link, so that After Effects and Prelude, for example, could add markers to a clip and those markers would ripple across all instances of that clip in the different applications. It's a great feature which we take advantage of here from time to time.
So what's the solution?
My workaround in CS6, which does not solve the issue of needing to merge clip markers so that an editor's markers and an assistant's markers can be applied to a single piece of media, was to turn off "write XMP ID to Files on Import." This would generate an XMP sidecar file which could be easily passed along with a project file to the remote editor, who could then overwrite his local XMP sidecars with the new ones containing the new marker info.
However, in Premiere CC that is no longer possible. It appears that if Premiere CC can access the XMP ID on a file, it will not generate a sidecar regardless of what you have set in your media preferences. We use ProRes Proxy as our dailies format (again, please no comments on this, it is not up for debate at this time) and Premiere can get to the XMP ID within the files and will not, no matter what it seems, generate an XMP sidecar.
We could change the company workflow to use DNxHD 36 instead of ProRes Proxy, which would give us XMP sidecars, but that would not solve the issue of needing to merge marker lists between projects non-destructively.
The best solution I can think of would be to have a script or some kind or built-in feature which would allow for the batch export, import and merging of marker lists. This way Adobe could keep its current clip-metadata-based marker workflow while giving professional users needing more flexible marker behavior the ability to have assistants non-destructively modify clip markers without necessitating the creation of extra media or project complexity.
I would really love some input on this and ideas from the pro community out there who has experience with shared project workflows - especially projects being shared remotely. There's not a lot of info out there about this and it would be great to hear what others are doing.
Thanks a million for sticking with this, if you've made it this far.
Best,
Jon

Thanks Jim,
I understand that Adobe Anywhere solves this, but there should be this fairly basic functionality (which exists in Avid and FCP) in a non-enterprise edition of the software. I have submitted a couple different feature requests about this, going back to CS5, so hopefully enough people make similar requests for a fix to be implemented. Adobe Anywhere is really not a solution for our small shop as currently configured/priced, especially when we can have editors working remotely with very affordable USB 3 drives. The only hangup is the markers, which just isn't worth a 5 figure fix. As such it's hard to consider the problem solved for either us or any small shop or post crew.
Best,
Jon

ProcessOrder API not populating the Price from the pricing attribute setup.

Hi,
I am having a problem while adding a line on the existing order through the Oe_Order_pub.Process_order API. A line is added but the pricing is not fetched using the pricing attribute.
I have passed calculate_Price_flag=’Y’ but in vain. I am not passing price list id but instead want to use a pricing attribute that will fetch the price on the item automatically.
But, it is working when I am calling this procedure from TOAD but when it is called through the Workflow, a line is added but no price is fetched.
Could anyone help me out on this? Here’s the code:
p_api_version_number NUMBER := 1.0;
p_init_msg_list VARCHAR2 (1) := FND_API.G_TRUE;
p_return_values VARCHAR2 (1) := FND_API.G_TRUE;
p_action_commit VARCHAR2 (1) := FND_API.G_FALSE;
x_return_status VARCHAR2 (1);
x_msg_count NUMBER := 0;
x_msg_data VARCHAR2 (2000);
p_header_rec oe_order_pub.header_rec_type:= oe_order_pub.g_miss_header_rec;
p_old_header_rec oe_order_pub.header_rec_type:= oe_order_pub.g_miss_header_rec;
p_header_val_rec oe_order_pub.header_val_rec_type:= oe_order_pub.g_miss_header_val_rec;
p_old_header_val_rec oe_order_pub.header_val_rec_type:= oe_order_pub.g_miss_header_val_rec;
p_header_adj_tbl oe_order_pub.header_adj_tbl_type:= oe_order_pub.g_miss_header_adj_tbl;
p_old_header_adj_tbl oe_order_pub.header_adj_tbl_type:= oe_order_pub.g_miss_header_adj_tbl;
p_header_adj_val_tbl oe_order_pub.header_adj_val_tbl_type:= oe_order_pub.g_miss_header_adj_val_tbl;
p_old_header_adj_val_tbl oe_order_pub.header_adj_val_tbl_type:= oe_order_pub.g_miss_header_adj_val_tbl;
p_header_price_att_tbl oe_order_pub.header_price_att_tbl_type:= oe_order_pub.g_miss_header_price_att_tbl;
p_old_header_price_att_tbl oe_order_pub.header_price_att_tbl_type:= oe_order_pub.g_miss_header_price_att_tbl;
p_header_adj_att_tbl oe_order_pub.header_adj_att_tbl_type:= oe_order_pub.g_miss_header_adj_att_tbl;
p_old_header_adj_att_tbl oe_order_pub.header_adj_att_tbl_type:= oe_order_pub.g_miss_header_adj_att_tbl;
p_header_adj_assoc_tbl oe_order_pub.header_adj_assoc_tbl_type:= oe_order_pub.g_miss_header_adj_assoc_tbl;
p_old_header_adj_assoc_tbl oe_order_pub.header_adj_assoc_tbl_type:= oe_order_pub.g_miss_header_adj_assoc_tbl;
p_header_scredit_tbl oe_order_pub.header_scredit_tbl_type:= oe_order_pub.g_miss_header_scredit_tbl;
p_old_header_scredit_tbl oe_order_pub.header_scredit_tbl_type:= oe_order_pub.g_miss_header_scredit_tbl;
p_header_scredit_val_tbl oe_order_pub.header_scredit_val_tbl_type:= oe_order_pub.g_miss_header_scredit_val_tbl;
p_old_header_scredit_val_tbl oe_order_pub.header_scredit_val_tbl_type:= oe_order_pub.g_miss_header_scredit_val_tbl;
p_line_tbl oe_order_pub.line_tbl_type:= oe_order_pub.g_miss_line_tbl;
p_old_line_tbl oe_order_pub.line_tbl_type:= oe_order_pub.g_miss_line_tbl;
p_line_val_tbl oe_order_pub.line_val_tbl_type:= oe_order_pub.g_miss_line_val_tbl;
p_old_line_val_tbl oe_order_pub.line_val_tbl_type:= oe_order_pub.g_miss_line_val_tbl;
p_line_adj_tbl oe_order_pub.line_adj_tbl_type:= oe_order_pub.g_miss_line_adj_tbl;
p_old_line_adj_tbl oe_order_pub.line_adj_tbl_type:= oe_order_pub.g_miss_line_adj_tbl;
p_line_adj_val_tbl oe_order_pub.line_adj_val_tbl_type:= oe_order_pub.g_miss_line_adj_val_tbl;
p_old_line_adj_val_tbl oe_order_pub.line_adj_val_tbl_type:= oe_order_pub.g_miss_line_adj_val_tbl;
p_line_price_att_tbl oe_order_pub.line_price_att_tbl_type:= oe_order_pub.g_miss_line_price_att_tbl;
p_old_line_price_att_tbl oe_order_pub.line_price_att_tbl_type:= oe_order_pub.g_miss_line_price_att_tbl;
p_line_adj_att_tbl oe_order_pub.line_adj_att_tbl_type:= oe_order_pub.g_miss_line_adj_att_tbl;
p_old_line_adj_att_tbl oe_order_pub.line_adj_att_tbl_type:= oe_order_pub.g_miss_line_adj_att_tbl;
p_line_adj_assoc_tbl oe_order_pub.line_adj_assoc_tbl_type:= oe_order_pub.g_miss_line_adj_assoc_tbl;
p_old_line_adj_assoc_tbl oe_order_pub.line_adj_assoc_tbl_type:= oe_order_pub.g_miss_line_adj_assoc_tbl;
p_line_scredit_tbl oe_order_pub.line_scredit_tbl_type:= oe_order_pub.g_miss_line_scredit_tbl;
p_old_line_scredit_tbl oe_order_pub.line_scredit_tbl_type:= oe_order_pub.g_miss_line_scredit_tbl;
p_line_scredit_val_tbl oe_order_pub.line_scredit_val_tbl_type:= oe_order_pub.g_miss_line_scredit_val_tbl;
p_old_line_scredit_val_tbl oe_order_pub.line_scredit_val_tbl_type:= oe_order_pub.g_miss_line_scredit_val_tbl;
p_lot_serial_tbl oe_order_pub.lot_serial_tbl_type:= oe_order_pub.g_miss_lot_serial_tbl;
p_old_lot_serial_tbl oe_order_pub.lot_serial_tbl_type:= oe_order_pub.g_miss_lot_serial_tbl;
p_lot_serial_val_tbl oe_order_pub.lot_serial_val_tbl_type:= oe_order_pub.g_miss_lot_serial_val_tbl;
p_old_lot_serial_val_tbl oe_order_pub.lot_serial_val_tbl_type:= oe_order_pub.g_miss_lot_serial_val_tbl;
p_action_request_tbl oe_order_pub.request_tbl_type := oe_order_pub.g_miss_request_tbl;
x_header_rec oe_order_pub.header_rec_type;
x_header_val_rec oe_order_pub.header_val_rec_type;
x_header_adj_tbl oe_order_pub.header_adj_tbl_type;
x_header_adj_val_tbl oe_order_pub.header_adj_val_tbl_type;
x_header_price_att_tbl oe_order_pub.header_price_att_tbl_type;
x_header_adj_att_tbl oe_order_pub.header_adj_att_tbl_type;
x_header_adj_assoc_tbl oe_order_pub.header_adj_assoc_tbl_type;
x_header_scredit_tbl oe_order_pub.header_scredit_tbl_type;
x_header_scredit_val_tbl oe_order_pub.header_scredit_val_tbl_type;
x_line_tbl oe_order_pub.line_tbl_type;
x_line_val_tbl oe_order_pub.line_val_tbl_type;
x_line_adj_tbl oe_order_pub.line_adj_tbl_type;
x_line_adj_val_tbl oe_order_pub.line_adj_val_tbl_type;
x_line_price_att_tbl oe_order_pub.line_price_att_tbl_type;
x_line_adj_att_tbl oe_order_pub.line_adj_att_tbl_type;
x_line_adj_assoc_tbl oe_order_pub.line_adj_assoc_tbl_type;
x_line_scredit_tbl oe_order_pub.line_scredit_tbl_type;
x_line_scredit_val_tbl oe_order_pub.line_scredit_val_tbl_type;
x_lot_serial_tbl oe_order_pub.lot_serial_tbl_type;
x_lot_serial_val_tbl oe_order_pub.lot_serial_val_tbl_type;
x_action_request_tbl oe_order_pub.request_tbl_type;
i NUMBER := 1;
x_data VARCHAR2(2000);
x_index NUMBER;
x_err_msg VARCHAR2(4000);
x_user_id NUMBER;
x_appl_id NUMBER;
x_resp_id NUMBER;
X_DEBUG_FILE Varchar2(400);
BEGIN
oe_msg_pub.initialize();
oe_debug_pub.initialize;
X_DEBUG_FILE := OE_DEBUG_PUB.Set_Debug_Mode('FILE');
oe_debug_pub.SetDebugLevel(3);
-- INITIALIZATION REQUIRED FOR R12
MO_GLOBAL.INIT('ONT');
MO_GLOBAL.SET_ORG_CONTEXT(p_org_id,'','ONT');
p_header_rec := OE_ORDER_PUB.G_MISS_HEADER_REC;
p_action_request_tbl(i) := OE_ORDER_PUB.G_MISS_REQUEST_REC;
p_line_tbl.delete;
p_action_request_tbl.delete;
p_line_tbl (i) := OE_ORDER_PUB.G_MISS_LINE_REC;
p_line_tbl (i).operation := OE_GLOBALS.G_OPR_CREATE;
p_line_tbl (i).header_id := p_header_id;
p_line_tbl (i).ordered_quantity := p_qty;
p_line_tbl (i).line_number := p_line_number;
p_line_tbl (i).shipment_number := 1;
p_line_tbl (i).calculate_price_flag := 'Y';--p_calc_price_flag;
p_line_tbl (i).created_by := p_user_id ;
p_line_tbl (i).creation_date := SYSDATE ;
p_line_tbl (i).inventory_item_id := p_item_id;
p_line_tbl (i).last_update_date := SYSDATE;
--p_line_tbl (i).last_update_login        := -1;
p_line_tbl (i).last_updated_by := p_user_id ;
p_line_tbl (i).line_type_id := p_line_type_id;
p_line_tbl (i).order_quantity_uom := p_qty_uom;
p_line_tbl (i).org_id := p_org_id;
--p_line_tbl (i).price_list_id            := p_price_list_id;
p_line_tbl (i).ship_from_org_id := p_ship_from_org_id ;
p_line_tbl (i).ship_to_contact_id := p_ship_to_contact_id;
p_line_tbl (i).ship_to_org_id := p_ship_to_org_id;
p_line_tbl (i).sold_from_org_id := p_sold_from_org_id ;
p_line_tbl (i).sold_to_org_id := p_sold_to_org_id;
p_line_tbl (i).subinventory := p_subinventory ;
--p_line_tbl (i).unit_list_price          := p_price;
--p_line_tbl (i).unit_selling_price       := p_price;
p_line_tbl (i).booked_flag := 'Y';
p_line_tbl(i).flow_status_code := 'CLOSED';
--SAVEPOINT BEFORE_PROC_API;
OE_ORDER_PUB.PROCESS_ORDER (
p_api_version_number => p_api_version_number
,p_init_msg_list => p_init_msg_list
,p_return_values => p_return_values
,p_action_commit => p_action_commit
,p_header_rec => p_header_rec
,p_old_header_rec => p_old_header_rec
,p_header_val_rec => p_header_val_rec
,p_old_header_val_rec => p_old_header_val_rec
,p_header_adj_tbl => p_header_adj_tbl
,p_old_header_adj_tbl => p_old_header_adj_tbl
,p_header_adj_val_tbl => p_header_adj_val_tbl
,p_old_header_adj_val_tbl => p_old_header_adj_val_tbl
,p_header_price_att_tbl => p_header_price_att_tbl
,p_old_header_price_att_tbl => p_old_header_price_att_tbl
,p_header_adj_att_tbl => p_header_adj_att_tbl
,p_old_header_adj_att_tbl => p_old_header_adj_att_tbl
,p_header_adj_assoc_tbl => p_header_adj_assoc_tbl
,p_old_header_adj_assoc_tbl => p_old_header_adj_assoc_tbl
,p_header_scredit_tbl => p_header_scredit_tbl
,p_old_header_scredit_tbl => p_old_header_scredit_tbl
,p_header_scredit_val_tbl => p_header_scredit_val_tbl
,p_old_header_scredit_val_tbl => p_old_header_scredit_val_tbl
,p_line_tbl => p_line_tbl
,p_old_line_tbl => p_old_line_tbl
,p_line_val_tbl => p_line_val_tbl
,p_old_line_val_tbl => p_old_line_val_tbl
,p_line_adj_tbl => p_line_adj_tbl
,p_old_line_adj_tbl => p_old_line_adj_tbl
,p_line_adj_val_tbl => p_line_adj_val_tbl
,p_old_line_adj_val_tbl => p_old_line_adj_val_tbl
,p_line_price_att_tbl => p_line_price_att_tbl
,p_old_line_price_att_tbl => p_old_line_price_att_tbl
,p_line_adj_att_tbl => p_line_adj_att_tbl
,p_old_line_adj_att_tbl => p_old_line_adj_att_tbl
,p_line_adj_assoc_tbl => p_line_adj_assoc_tbl
,p_old_line_adj_assoc_tbl => p_old_line_adj_assoc_tbl
,p_line_scredit_tbl => p_line_scredit_tbl
,p_old_line_scredit_tbl => p_old_line_scredit_tbl
,p_line_scredit_val_tbl => p_line_scredit_val_tbl
,p_old_line_scredit_val_tbl => p_old_line_scredit_val_tbl
,p_lot_serial_tbl => p_lot_serial_tbl
,p_old_lot_serial_tbl => p_old_lot_serial_tbl
,p_lot_serial_val_tbl => p_lot_serial_val_tbl
,p_old_lot_serial_val_tbl => p_old_lot_serial_val_tbl
,p_action_request_tbl => p_action_request_tbl
,x_header_rec => x_header_rec
,x_header_val_rec => x_header_val_rec
,x_header_adj_tbl => x_header_adj_tbl
,x_header_adj_val_tbl => x_header_adj_val_tbl
,x_header_price_att_tbl => x_header_price_att_tbl
,x_header_adj_att_tbl => x_header_adj_att_tbl
,x_header_adj_assoc_tbl => x_header_adj_assoc_tbl
,x_header_scredit_tbl => x_header_scredit_tbl
,x_header_scredit_val_tbl => x_header_scredit_val_tbl
,x_line_tbl => x_line_tbl
,x_line_val_tbl => x_line_val_tbl
,x_line_adj_tbl => x_line_adj_tbl
,x_line_adj_val_tbl => x_line_adj_val_tbl
,x_line_price_att_tbl => x_line_price_att_tbl
,x_line_adj_att_tbl => x_line_adj_att_tbl
,x_line_adj_assoc_tbl => x_line_adj_assoc_tbl
,x_line_scredit_tbl => x_line_scredit_tbl
,x_line_scredit_val_tbl => x_line_scredit_val_tbl
,x_lot_serial_tbl => x_lot_serial_tbl
,x_lot_serial_val_tbl => x_lot_serial_val_tbl
,x_action_request_tbl => x_action_request_tbl
,x_return_status => x_return_status
,x_msg_count => x_msg_count
,x_msg_data => x_msg_data
p_status := x_return_status;
IF x_return_status != apps.fnd_api.g_ret_sts_success THEN
x_err_msg:= 'API Error Occured while creating Recycle Fees line ' ;
FOR i in 1..x_msg_count
LOOP
OE_MSG_PUB.GET(i,'F',x_data,x_index);
x_err_msg := x_err_msg || x_data ;
END LOOP;
p_error := x_err_msg;
insert into xx_test values('API ERR: '||SYSDATE|| p_error);
-- ROLLBACK TO SAVEPOINT BEFORE_PROC_API;
END IF;
EXCEPTION
WHEN OTHERS THEN
-- ROLLBACK TO SAVEPOINT BEFORE_PROC_API;
p_error := 'Error Occured in Order Line API: '||SYSDATE||substr(SQLERRM,1,250) ;
p_status := 'E';
END call_order_api;
Thanks,
Rahul

Another striking feature here is, the API works absolutely well for the Internal Orders (Book--> Release-->Ship) but price is not pulled for the External Drop Ship Orders.

11.5.10.2 Workflow-only users licensing

Hi,
I have a question on licensing required for the users who only have a 'Workflow user' responsibility in OEBS, version 11.5.10.2.
We'd like to start using iExpenses, but currently lots of potential approvers do not have any access in OEBS, I wonder how much it could cost us to create them in the system as a workflow-only users. Any references to Oracle's pricing policy on the subject are welcome.
Thanks,
Vadim

Please contact your Oracle Sales representative; he/she is the best one to answer Oracle License questions.
You may review these links and see if it helps.
Global Pricing and Licensing
http://www.oracle.com/us/corporate/pricing/index.html
Oracle Price Lists
http://www.oracle.com/us/corporate/pricing/price-lists/index.html
Thanks,
Hussein

Best Practice for Conversion Workflow

Hello,
I'm converting video files from our "home grown" virtual media reserve to iTunes U. Some of the files are in RM format, some are already compressed .mov's (not H.264) and some I have the original DV files for.
Anyone out there have a best practice for converting these file types for posting to iTunes U? I have Final Cut Studio (Compressor), QT Pro and Squeeze available to me.
Any experience you have with this would be helpful.
Thanks,
Jeana

For converting old files to a podcast compatible video and based on the machine you have, consider elgato turbo.264. It is a fairly priced "co-processor" for video conversion. It is comprised of an application and a small USB device with a encoder chip in it. In my experience, it is the fastest way to create podcast video files. The amount of time that you will save will pay for the device quickly (about $100). Plus it does batch conversion of any video that your system currently plays through QuickTime. it has all the necessary presets and you can create your own. It has a few minor limitations such as not supporting (at this moment) enhanced podcasting features such as chapter markers and closed-captions but since you have old files for conversion, that won't matter.
For creating new content, the workflow varies a lot. Since you mention MP3s, I guess you are also interested in audio files. I would stick with GarageBand, especially if you are a beginner plus it supports enhanced podcasts.
In any case the most important goal is to have the simplest and fastest way to go from recording to publication. The less editing the better. To attain that, the best methods will require the largest investments. For example, for video production the best way is to produce the content live so when you finish recording it is only a matter of encoding and publishing. that will require the use of a video switcher that can ingest at least one video camera and a computer output to properly capture presentation material. That's the minimum. there are several devices that can do this for you. Some are disguised PCs and some connect to a PC for tapeless recording. You can check the Tricaster, which I like but wish it was a Mac and not a Windows Xp PC. Other routes may include video mixers from manufacturers like Edirol, Pansonic or Sony connected to a VTR or directly to a Mac for direct-ti-disc capture. I f you look at some of the content available in iTunes U, you will see what I explain here. This workflow requires preparation and sufficient live support but you will have your material ready for delivery almost immediately after the recorded event. No editing required. Finally, the most intensive workflow is to record everything separately and edit it later, which is extremely time consuming.

Need to find a workflow for the following business process

dear expert:
as we have SD,MM,PP for multiple plant and everybodys work is interdependent with others we find highly challenging to make it synchronised. to manage the situation i thought if we can create an workflow where every event of individual person will trigger and send notification to other members to start his job. the following is a scenerio where i tried to show the sequence of work and respective user module as responsible. please suggest is there any workflow to control the same in sap.
Style
Color
FG create     SD
Customer info record     SD
Pricing master     SD
Ref. Bom     SD
Contract     SD
Create Sales order     SD
Create PP matetial (Cut Pnl, Print Pnl, Emb Pnl, Sweing gmt)     PP
Create PP BOM(Create different BOM for Dfferent Material)     PP
Create Routing     PP
MRP run     PP
Purchase Requisition     MM
Purchase Order     MM

Dear,
If you have ABAP team with you, an email to user SAP inbox will trigger from each transaction.
We implemented this for PR level for each 1200 individual user / management release authorities, which informs by an email about the status of PR. once the final release done based on purchase group - an email will trigger to central procurement department all responsible persons indicating purchase order awaiting.
NOW material rejection - reference to 122 and 102 movement is under study. Once any material rejected the system send email to procurement, stores personnel and management informing the material was rejected.
Similar, based on the presentations and indepth meeting held with ABAP and FUNCTIONAL teams, workflow can be trigger on each event (not sure the all processes you mentioned in your post). But I hope possibility exists.
THE ONLY POINT YOU SHOULD KEEP IN MIND AND INFORM MANAGEMENT - SYSTEM PERFORMANCE WILL AFFECT A LOT. SYSTEM WILL SLOW DOWN AS MANY WORKFLOWS EXISTS. CONSULT BASIS TEAM ALSO.
Regards,
Syed Hussain.

Pricing item not available error

Hi Gurus ,
The workflow for some purchase orders in our system wnet into error . And the workflow error log says 'Pricing item not available ' .
I checked the IPC and it was active.
Problem is we are getting this issue quite often now , although it only effects 2-3 POs every time it happens (once or twice in a month ) .Could you please tell me what could the root cause of this issue ? What can be done to avoid this in future ?
Please note that all such POs, when re-ordered , are transfered successfully to backend system.
Also , sometimes for shopping carts too , we get this error ( in SM58 Tcode ) " BBP_PD_SC_TRANSFER NONE DD.MM.YYYY HH:MM:SS Pricing item not available".
Regards,
Saurav

Hello All ,
Could you please reply to these ?
Regards
Saurav

11.5.10: RETROACTIVE PRICING이 WORKFLOW를 통해 수행되지 않을 경우 처리 방법

Similar Messages

Maybe you are looking for