Transaction Key for freight price differences while invoicing?

Hi all,
Which is the transaction key (of the OBYC) in case of freight price differences while invoicing?
I mean, in case of price differences of the below entry, which is the transaction key for those differences?
Purchasing freight account FRE
Thanks!

Hi,
I will explain how accounts will hit for the Freight.
1)
At the time of MIGO Inventory account debit
                              Freight Inward account Credit.
At the time of Invoice Vendor account Credit
                                  Freight Inward account Debit.
2)
If u r not done MIGO for Freight(Means u r not included Freight cost at the time MIGO in PO) so at the time of Invoice
                           Vendor account Credit
                           Inventory account debit
2A)If at the time of Invoice verification Material not available in the stock that time it will hit
Vendor account Credit
Price difference Account debit
Thanks,
Raghu

Similar Messages

Account / Transaction key for Services

Dear Sappers,
I am maintaining a condition for services. IMG MM - External Services Management -> Maintain Condition for services . Here i have created condition type and maintained in conditions: Schemas for services. But i cannot create Account key / Transaction key here. Can anyone guide me where i can create account / transaction key for external service management.
Account / Transaction key can be maintained for normal PO conditions in IMG MM -> Purchasing -> Conditions -> Price Determination but those account keys are not appearing in External Service Management calculation schema for services.
Thanks.
Shahzad Shakoor

Using OMGH the transaction key can be maintained but it doesnt appears in Service Management calculation schema.
Using SM30 V_T687 transaction key is maintained and it is accepted in Service Management caculation schem but now i have to assign GL accoutn to it.
Kindly guide me where i can assign GL account for this newly created transaction key as this one is not appearing in OBYC.
Thanks a lot.

Expense for the price difference by reversing entry of goods

Hi Experts,
There is an Expense for the price difference by reversing entry of goods. Conceptually is this correct?
Thanks in advance.
José Luis

Hi
Price difference during reversal of GR may be correct due to the change in price between GR & reversal.
It depends on price control whether S-Std price or V-Moveing average price in the Material Master accounting view.
Karthik

Transaction key for account determination

Hi guru,
i would like to add a new transaction key for account determination to fullfil a business process .
Could you help me to find out the Transaction code in customizing?
A prompt reply is appreciated.
Thanks in advance
Vir

Dear Vir,
The G/L account determination process in G/L Accounting mostly uses the
transaction key technique to obtain the required G/L accounts for business transactions.
For Foreign currency transactions:
SPRO -> Financial Accounting -> General Ledger Accounting -> Periodic Processing -> Valuate -> Foreign Currency Valuation
Other General Ledger Transactions
SPRO -> Financial Accounting -> General Ledger Accounting -> Business Transactions -> Closing -> Carried Forward -> Define Retained Earning Account
OBA1 G/L account determination for foreign currency valuation
OBYA Maintain inter-company clearing G/L accounts
OB53 Maintain retained earnings accounts
OBBV Assign AR/AP adjustment accounts
OBXD Maintain bad debt reserve accounts
ACACAD Accrual account determination ( simple or extended )
ACACADMETASGL Accrual account determination strategy
ACACTREE01 Create accrual objects
Pricing:
        V/09    Condition Types: Account Determin.
        V/10    Account Determination: Access Seqnc
        V/11    Conditions: Account Determin.Proced.
        V/12    Account Determination: Create Table
        V/13    Account Determination: Change Table
        V/14    Account Determination: Display Table
G/L Accounts in MM Account Determination:
The program RM07C030 check all the G/L account define in your Material Master valuation class.
Search is via Company code and Valuation area.
Visit the following link for more information:
http://www.sapscene.com/sapscene/accassg.html#SD-FI%20Account%20Determination
Reward points if this is helpful.
Regards,
Naveen.

Transaction Key for Purchase Account

Hi Dear All,
I want ti define another Purchase account key for frieght like FRE.
How to creat it?
Regards
Gitesh

Hi Gitesh,
We won't assign Purchase A/C keys in Pricing Procedure.
Normally we activate Purchase A/C posting @ company code level under the following settings.
SPRO - MM - Valuation and Account Assignment - Account Determination - Account Determination Without Wizard - Purchase Account Management.
As I have already mentioned above system uses the Standard transaction key EIN & EKG for Purchase A/C postings.
I dont think we have the option to change this standard one.
Now if your requirement is to use a different transaction key instead of FRE then create a new trans.key & assign the same to the freight condition type in Pricing Procedure.
Hope its clear.
Thanks & Regards,

Transaction Key for Movement Type 561

Hello,
For movement type 561, I know one of the Transaction Key is BSX. I would like to ask what is the other Transaction Key as I would like to set the GL Account Determination. Thanks.
Thanks.

Hi
Transaction keys required for 561 movemnt type are
BSX - For the inventory posting
GBB - BSA - For initial entry of stock balances
For performing the 561 movment G/L account needs to be assigned to both these transaction keys.
Thanks & Regards
Kishore

How to know debit and credit transaction key for movement type

Hi,
With T. code OMWB account assignment simulation we can see all the accounts which are involve for debit and credit enties but I want to know is there any T. code or method with which we can know which transaction key will be debit and which will be credited like for movement type 101 the transaction keys are GBB, BSX WRX etc. i want o know whethere GBB a

Hi,
Thanks for your reply, but with this we can see the for GBB which is the credit account and which account is use for debit entry, like this for all transaction event key like WRX, BSX etc. we can see the G/L account use for Debit and credit, but i want to know for particular selction of Plant, material , movement type, my GBB account will have entry in debit account or credit account How we can know this.
regards,
zafar

HT1491 My daughter accidentally tap the HD version instead of the SD version because I have an older IPhone version. Can I have a refund for the price difference?

My daughter accidentally tap the HD version instead of the SD version of the tv episode we're downloading. I have IPhone 3G. Can we stop the download? Also can we refund the price difference between HD & SD version?

All sales are final.
You can try contacting itunes support and asking for an exception:
http://www.apple.com/support/itunes/contact/

Price difference in Invoice

Hello Gurus,
Can anyone please suggest on the systems unknown behaviour given below.
We have scheduling agreement in currency GBP and Local currency EUR, when we post GR, it is getting posted perfectly to Inventory account to GR IR account. But when we post the Invoice system is crediting the same GRIR amount to vendor account which is right and debiting a huge unknown figure to Price difference account and the difference between these is getting credited to GRIR account. This is completely out of logic.
Exchange rates are perfectly ok. when we create a scheduling agreement with the same data it is working fine. now I am now able to find out where the problem is can anyone suggest on this.
Thank you,
Srinivas

Check the standard cost of the material, looks like something is terribly wrong like it is per 1 instead of per 1000 or something like that which might explain the huge posting you see to the price difference account during invoicing. I am sure it will be there in the GR accounting document too..

To fetch process instance key for Modify Provisioned Resource while request

Hi,
I am trying "Self Modify Provisioned Resource" through Request and multiple resource object is assigned to the user.I have a requirement to a develop validator code to compare old data and request data and take action accordingly.How to get the Process Instance Key or OIU Key of the resource w.r.t user, so that i can compare the data entered in dataset to the data in process form and do the modify operation accordingly.
I am working on OIM 11.1.1.5 version and have applied BP03 patch also.
-Neha Gupta
Edited by: 912833 on Sep 11, 2012 2:26 AM
Edited by: 912833 on Sep 11, 2012 2:28 AM

More or less you can use the following:
resultGetObjects = userOperationsIntf.getObjects(plUserKey);
            int countResultGetObjects = resultGetObjects.getRowCount();
            logger.debug("CommonProvisioning.updateProcessForm Object Count = " + countResultGetObjects);
            for (int j = countResultGetObjects; --j >= 0;) {
                resultGetObjects.goToRow(j);
                String objName = resultGetObjects.getStringValue("Objects.Name");
                String status = resultGetObjects .getStringValue("Objects.Object Status.Status");
                if (resourceObjName.equalsIgnoreCase(objName) && "Provisioned".equalsIgnoreCase(status)) {
                    prntPrvsndPrsInsKey = resultGetObjects .getLongValue("Process Instance.Key");
                     break;
            }HTH,
BB

Advanced search for a price range while checking for an empty values using php in DW

I am creating an advanced search with DW php. I would like to submit a search where some entrys can be left black. So checking for empty values (which I have managed, thank you David Powel), however when searching between multiple price ranges does not seem to work.
please see attached forms:
The search page:
<form action="Detailed-Search-Result.php" method="get" target="_self"><table width="90%" border="0" cellspacing="0" cellpadding="2">
<tr>
    <td colspan="2"><label for="Detailed Search">Advanced Search</label></td>
    </tr><tr>
    <td><label for="Product">Product:</label>
      </td>
    <td><select name="Category" id="Category">
      <option value=></option>
        <option value="Keyboard">Keyboard</option>
        <option value="Piano">Piano</option>
      </select></td>
</tr>
<tr>
    <td><label for="Make">Make:</label>
    </td>
    <td><select name="Manufacturer">
      <option value=></option>
      <option value="Boss">Boss</option>
      <option value="Casio">Casio</option>
      <option value="Kawai">Kawai</option>
      <option value="Ketron">Ketron</option>
      <option value="Korg">Korg</option>
      <option value="Roland">Roland</option>
      <option value="Samson">Samson</option>
      <option value="Yamaha">Yamaha</option>
    </select></td>
</tr>
<tr>
    <td><label for="Color">Color:</label></td>
    <td><select name="Color">
      <option value=></option>
      <option value="Black">Black</option>
      <option value="Cherry">Cherry</option>
      <option value="Mahogany">Mahogany</option>
      <option value="Polished Eboney">Polished Eboney</option>
      <option value="Rosewood">Rosewood</option>
      <option value="White">White</option>
      <option value="Red">Red</option>
    </select></td>
</tr>
<tr>
    <td><label for="Price">Price:</label></td>
    <td><select name="Price">
      <option value=></option>
      <option value="0-500">£0-500</option>
      <option value="500-1000">£500-1000</option>
      <option value="1000-2000">£1000-2000</option>
      <option value="2000">£2000></option>
    </select></td>
</tr>
<tr>
    <td colspan="2">
      <input name="Search2" type="submit" id="Search2"></td>
    </tr>
    </table>
</form>
The results page
$varCategory_rsgetsearch2 = "%";
if (isset($_GET['Category'])) {
$varCategory_rsgetsearch2 = $_GET['Category'];
$varMake_rsgetsearch2 = "%";
if (isset($_GET['Manufacturer'])) {
$varMake_rsgetsearch2 = $_GET['Manufacturer'];
$varColor_rsgetsearch2 = "%";
if (isset($_GET['Color'])) {
$varColor_rsgetsearch2 = $_GET['Color'];
$varPrice_rsgetsearch2 = "%";
if (isset($_GET['Price'])) {
$varPrice_rsgetsearch2 = $_GET['Price'];
mysql_select_db($database_dBconn, $dBconn);
$query_rsgetsearch2 = 'SELECT * FROM products';
$where = false;
if (isset($_GET['Category']) && !empty($_GET['Category'])) {
$query_rsgetsearch2 .= ' WHERE Category LIKE varCategory '. GetSQLValueString($_GET['Category'], 'text');
$where = true;
if (isset($_GET['Manufacturer']) && !empty($_GET['Manufacturer'])) {
if ($where) {
   $query_rsgetsearch2 .= ' AND ';
} else {
   $query_rsgetsearch2 .= ' WHERE ';
    $where = true;
$query_rsgetsearch2 .= 'Manufacturer LIKE varManufacturer ' . GetSQLValueString($_GET['Manufacturer'], 'text');
if (isset($_GET['Color']) && !empty($_GET['Color'])) {
    if ($where) {
   $query_rsgetsearch2 .= ' AND ';
} else {
   $query_rsgetsearch2 .= ' WHERE ';
    $where = true;
$query_rsgetsearch2 .= 'Color LIKE varColor ' . GetSQLValueString($_GET['Color'], 'text');
if (isset($_GET['Price']) && !empty($_GET['Price'])) {
    if ($where) {
   $query_rsgetsearch2 .= ' AND ';
} else {
   $query_rsgetsearch2 .= ' WHERE ';
    $where = true;
switch( $_GET['Price'] ){
        case '0-500':
        $query_rsgetsearch2 .= ' RRP BETWEEN 0 AND 500 ORDER BY price ASC'. GetSQLValueString($_GET['Price'], 'text');
        break;
          case '500-1000':
        $query_rsgetsearch2 .= ' RRP BETWEEN 500 AND 1000 ORDER BY price ASC'. GetSQLValueString($_GET['Price'], 'text');
        break;
                    case '1000-2000':
        $query_rsgetsearch2 .= ' RRP BETWEEN 1000 AND 2000 ORDER BY price ASC'. GetSQLValueString($_GET['Price'], 'text');
        break;
          case '2000':
       $query_rsgetsearch2 .= ' RRP BETWEEN 2000 AND 10000 ORDER BY price ASC'. GetSQLValueString($_GET['Price'], 'text');
        break;
$query_rsgetsearch2 = sprintf("SELECT * FROM products WHERE Category LIKE %s AND products.Manufacturer LIKE %s AND products.Color LIKE %s", GetSQLValueString("%" . $varCategory_rsgetsearch2 . "%", "text"),GetSQLValueString("%" . $varMake_rsgetsearch2 . "%", "text"),GetSQLValueString("%" . $varColor_rsgetsearch2 . "%", "text"));
$query_limit_rsgetsearch2 = sprintf("%s LIMIT %d, %d", $query_rsgetsearch2, $startRow_rsgetsearch2, $maxRows_rsgetsearch2);
$rsgetsearch2 = mysql_query($query_limit_rsgetsearch2, $dBconn) or die(mysql_error());
$row_rsgetsearch2 = mysql_fetch_assoc($rsgetsearch2);
I would be greatfull for any help

I have managed to solve the problem.
In the end I didn't check if the values were empty, as it worked fine without. However the switch of the price didn't work in combination with the rest of the query.
I've solved the problem as follows:
$varCategory_rsgetsearch2 = "%";
if (isset($_GET['Category'])) {
$varCategory_rsgetsearch2 = $_GET['Category'];
$varMake_rsgetsearch2 = "%";
if (isset($_GET['Manufacturer'])) {
$varMake_rsgetsearch2 = $_GET['Manufacturer'];
$varColor_rsgetsearch2 = "%";
if (isset($_GET['Color'])) {
$varColor_rsgetsearch2 = $_GET['Color'];
$varPrice_rsgetsearch2 = "%";
if (isset($_GET['Keysound_price'])) {
$varPrice_rsgetsearch2 = $_GET['price'];
mysql_select_db($database_dBconn, $dBconn);
$query_rsgetsearch2 = sprintf("SELECT * FROM products WHERE Category LIKE %s AND products.Manufacturer LIKE %s AND products.Color LIKE %s", GetSQLValueString("%" . $varCategory_rsgetsearch2 . "%", "text"),GetSQLValueString("%" . $varMake_rsgetsearch2 . "%", "text"),GetSQLValueString("%" . $varColor_rsgetsearch2 . "%", "text") );
switch( $_GET['price'] ){
        case '0-500':
        $query_rsgetsearch2 .= ' AND price BETWEEN 0 AND 500 ORDER BY price ASC';
        break;
          case '500-1000':
        $query_rsgetsearch2 .= ' AND price BETWEEN 500 AND 1000 ORDER BYprice ASC';
        break;
                    case '1000-2000':
        $query_rsgetsearch2 .= ' AND price BETWEEN 1000 AND 2000 ORDER BY price ASC';
        break;
          case '2000':
        $query_rsgetsearch2 .= ' AND price BETWEEN 2000 AND 10000 ORDER BY price ASC';
        break;
$query_limit_rsgetsearch2 = sprintf("%s LIMIT %d, %d", $query_rsgetsearch2, $startRow_rsgetsearch2, $maxRows_rsgetsearch2);
$rsgetsearch2 = mysql_query($query_limit_rsgetsearch2, $dBconn) or die(mysql_error());
$row_rsgetsearch2 = mysql_fetch_assoc($rsgetsearch2);
I'm sure that you can keep the checking for values in, however for me the was no need for it anymore.
Thanks for all your help

Invoice for price difference

I created a PO and did GR & IV on the PO price.
(In the mean time, price of the material changes but the bill was raised on original PO price.)
Now the Vendor sends another Bill for the price difference.
I want to create Invoice for that Bill price.
How shall I do that?
regards,
VS

Hi
You can use subsequent credit/debit option.
please check this:
http://help.sap.com/saphelp_47x200/helpdata/en/a8/b99725452b11d189430000e829fbbd/content.htm
regards
Srinivas

Price difference in PO-invoice to different Consumer Account

Hello,
I have the following situation:
Purchase Order: 10 units x 1000 USD = 10000     (Account assigned : u201CKu201D)
Goods Receipt: 10 units (x 1000 USD) = 10000    (valuated GR against consumer account)
PO u2013 invoice:     10 unitos x 1100 USD = 11000     (Invoice with price difference)
1) Upon GR u2013 Accounting document shows:
420021 (consumer account)     10000
220021 (GR/IR)          -10000
2) Upon entering the invoice, SAP standard makes the following account movements:
123456 (Vendor Account)       -11000
220021 (GR/IR) =             10000
420021 (Consumer Account)         1000       (Price difference) - Goes to the same consumer account !
I would like to know if I can configure in the invoice account determination a diferent consumer account for the price difference so that the acounting document will show:
123456 (Vendor Account)                           -11000
220021 (GR/IR) =             10000
420055 (Consumer Account)         1000       (Price difference) - a different consumer account !
Anyone did this before? How, is it standard config of OBYC or does one need a user-exit to accomplish this?
Thanks for any reply,
Aart

Hi guys,
Thanks for your replies.
I customized in the OBYC the price difference account PRD (for the Valuation Category of the material) even changed for the particular material the Price control in the Material Master from "V" to "S", but still, the difference upon receiving the invoice (MIRO) goes to the same Consumer Account!
Maybe the PRD account only works in Stock Postings. Im using POs account assigned (Cost Center).
Any clues?
Thanks,
Aart

PRD-Auto Post price differences to different price difference accounts

Dear all,
As I know, in Account Automatic Posting, the transaction key PRD is for Cost price Difference.
If I want to post price differences to different price difference accounts in the case of goods receipts for different cost in purchase orders, How can I configure it?
Example, in PO, there is 2 costs: Freight (F) and Insurance(I) are key in as Condition Type.
I would like to post price difference from F to account XXX, and price difference from I to account YYY.
Can I configure like this?
Thank you very much for your support!
Cao Huy

Hello,
What is price difference.
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 difference in genereal will not trigger for the materials with price control V ( Moving average price) but however
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
For you example, you have you are having PO with Freight (F) and Insurance(I), these are called pallned delivery costs, not Price difference,
so create two different condition type for Freight and insurance and assign two different G/L accounts for these condition types in account determination.
While posting system will hit perticular G/L acconut.
Regards
Mahesh Naik

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

Transaction Key for freight price differences while invoicing?

Similar Messages

Maybe you are looking for