Questions about Territory determination in Business transactions in CRM 7.0

Hi All,
We are in the process of configuring territory management in our system. I have a couple of questions regarding Territory determination in Business transactions in CRM 7.0.
1) Territories in business transactinos are determined based on partner function categories: employee and person responsible. If the employee is assigned to multiple territories, which territory is determined for the transaction.
a) Is it the territory for which he is assigned the 'Default territory' flag'?
b) What if the employee does not have any territories with the 'Default territory' set?
2) We have had SAP CRM since the last 6-7 years and recently upgraded to CRM 7.0. When I use the transaction searches in the Web UI using the search parameters 'Territory ID' and 'Territory description' we can't see any old transactions in the search results. We can only see the test transactions that were created after we ran the master data reln. update program CRM_TERRMAN_PROC_REL. Is there another program which updates transactional data relationships similar to the master data one?
Appreciate your inputs.
Regards,
Ramesh Nallabelli

Similar Messages

What is Business Transaction in CRM

Hi,
What is Business Transaction in CRM? What is deifference between partner and partner_guid? What is significance? and also product, prodcut_guid?
Thanks,
Shashikanth

Hi Shashikanth,
Most of the transaction that you carry out in CRM are Business Transaction. E.G. Service Contract, Activities, Lead, Task etc.
Business Transactions are further divided into Subobject Category, these Subobject Categories are again subdivided into Transaction Type.
Categorization of CRM Business Transaction based on Subobject Category
Business Transaction Name SUBOBJECT CATEGORY
Activity BUS2000126
Service Contract BUS2000112
Lead BUS2000108
Opportunity BUS2000111
Task BUS2000125
Utility contract item BUS2000147
Note:
1. For Example if you want to retrieve all the activities in CRM, pass the OBJECT_TYPE as BUS2000126 in CRMD_ORDER_INDEX table.
2. The Subobject Category can be customized for a business transaction from the transaction SPRO.
Partner : Partner is a 10 char number used to identify Business Partner in the system.
PArtner GUID : It is global unique identifier to identify the partner globally.
As such there is no difference in partner and partner guid, both refer to the same entity in CRM and are unique across the system. Refer the table BUT000.
Same applies to product and product guid. Refer the table CRMM_PRODUCT.
Reward points if it helps and close the thread.

Question about purchasing data of business partner in SRM 7.0

When we create vendor in ECC with transaction XK01, we can create pruchasing view and company code view of vendor.
But in SRM 7.0, I have not find any place abount company code and purchasing data about business partner?
Any one could provide some suggestions?
Tanks in advance!

Hi Justin,
As in previously releases, SRM 5.0 f.e., not all business partner data available in ECC is replicated in to the SRM procurement system (this can be enhanced via developments). The business partner structure in SAP SRM is different from the ECC business partner structure. SAP SRM business partner data only uses 1 view which holds all the data a vendor can have (BP function: vendor). There aren't any views/tabs in SRM.
Company code and purchasing data is determined via organisational schema (ppoma_bbp) and a company and purchasing organization have their own business partner master record in SAP SRM as well.
Note: Certain vendor business partner settings/parameters are better to maintain via the web transaction 'maintain business partner'.
Hope this helps.
Kind regards,
Tim
Edited by: T. Schuffelen on Mar 21, 2011 11:45 AM

Question about partner determination for customer master

Hi, experts,
I have already read the documentation about this topic at forum. Still I have the following question:
why should we assign the partner function to the account group? According to my understanding, the partner function has to be assigned to partner determination procedure and then through partner determination it is associated with the account group. If the partner can be assigned to account group directly, why do we still need determination procedure?
Best regards,
Fan

Hi
Let us consider an existing Partner Determination procedure in standard SAP.
The Partner Determination Procedure (e.g, ABCD) can contain multiple "Partner Functions". Suppose there are 100 numbers of Partner Functions in the Procedure.
We assign "Partner determination Procedure" to the "Account Group", so that , the assigned Procedure will be applicable for the Customer master data created under that Account group.
Suppose, Partner determination Procedure "ABCD" has been assigned to Account Group "XYZ".
Now, any Customer created under Account Group "XYZ", the Procedure "ABCD" will be applicable for them. Right?
We have already discussed , the Procedure "ABCD" contains 100 different "Partner Functions".
Out of these 100 Partner Functions, only those Partner Functions, which are permitted by the Account Group "XYZ" , they can only be entered in the Sales area data > Partner Function tab of the Customer master data.
Suppose, only 6 Partner functions (out of 100 no) are assigned to Account Group "XYZ".
So these 6 Partner Functions are permitted by the said Account Group "XYZ" and these 6 Partner Functions can only be entered in the Customer master data.
So, to summerise it, if you want to enter a Partner Function in the Customer master, then
- First, that Partner Function must be available in the Procedure which applicable, and
- Second, that Partner Function also must have been permitted (assigned) by the Account Group .
I hope, it is clarified.
Regards
Pradyumna

Question about Receiver Determination step in BPM

Hello all,
I have a BPM process similar to Multicat BPM Pattern.
I have some questions regarding how the Receiver Determination works:
1. Does it have to have interface determination in the Integration Directory?
2. Does that interface determination (including the mapping) takes place when sending a message to a receiver from that Receiver Determination step,
or should I perform a Mapping step explicitly in the process?
Thanks ahead,
Yoav.

Yoav,
Am not sure if I understood your requirement compltely.
Case A:If you are using a send step without a Transformation Step.
Then Send will have message A being sent out from BPm and then , during Interface Determiantion this will be transformed into Message B by Mapping in Interface Determination and this message B will be received by receiver
Case B:If you have a transform and then a Send
In this case, the mapping has been done, so you have the message B with you and so, them message sent from the BPM will be message BHope this clarifies,
Regards,
Bhavesh
Message was edited by: Bhavesh Kantilal

Question about sloc determination in MFBF and backflush in REM

Dear SAPper,
I just try to read about Repetitive Manufacturing and i came with some confused item.
1. I try to backflush MFBF and i don;t fill the planned order, but the backflush is succedd. Something
strange is my planned order is not decrease:(, so do i have to fill planned order number every time i backflush. Can i backflush anonymous to planned order number and the system derease the planned order automatically in FIFO manner
2. I configure the auto sloc determination and i have set maximum number of split unlimitted.
for example in MFBF i need 50 PC Raw Material
My stock in SLoc 1000 is 40 PCS
My stock in SLoc 2000 is 200 PCS
I configure the sloc determination like this
1. F 1000
2. F 2000
Nut in MFBF component always withdraw from 2000 with 50 (full quantity) although i set maximum number of split maximum
I tried batch determination before and it split.
Did i miss something so the system can split the quantity along sloc automatically
Please throw a light:D
Best regards,
Freddy Ha

Hi,
1)
Normally in the rem for backflush just u have to enter the product and qty then system will automatically reduces the planned order.
But in situation if planned order is not reducing then please check ur REM profile in the "control data2" tab
In this which one u have select for the planned order reduction.
2)
Regarding stock determination, create stock determination rule thr' T CODE:OXPS.
Here u have to create stock determination rule first from which storage location material should be picked, depending upon the priority.
Assign this stock determination rule in the material master or in the REM profile "Control data2 " tab.
Then system will automatically pick the material depending upon the stock determination rule.
Regards
Vijay

Another question about receiver determination

Hi friends
Can we add a new receiver to the list of receivers in the receiver determination , based in some condition only for this new receiver.
Let us say we have the message 1 sent to receiver_1 and receiver_2 no matter what , but the message 1 should only be sent to receiver_3 according to some conditions.
my question if I can only put condition for the receiver_3 receiver determination , or do i have to write a UDF for mapping of the receiveres.
Thanks

Can we add a new receiver to the list of receivers in the receiver determination , based in some condition only for this new receiver.
yes you can add list of the receivers in the receiver determination , based on some condition .
my question if I can only put condition for the receiver_3 receiver determination , or do i have to write a UDF for mapping of the receiveres.
dont need to write any UDF's . u have to use Context Object/X-Path for REC3 in rec.det
for ex: field1 = 1000 -> rec3
field1 =900 ->rec1
Edited by: bhavanisankar.solasu on Feb 10, 2012 3:48 PM

Authorization Check in Business Transactions in CRM 2007

Hi everybody, I have a problem whit the authorization check in CRM 2007.
This link help me to follow the steps
http://help.sap.com/saphelp_crm60/helpdata/en/e9/b29a39e7aee372e10000000a11
I follow this steps:
1.- Created a new single role on the PFCG
2.- On the Menu tab add the transaction BSP_CRMD_BUS2000108 (Trax for LEADS)
3.- On the authorization tab create a new profile and in the authorization data set the values for CRM_ORD_OP: PARTN_FCT 00000012, PARTN_FCTT *, ACTVT '02,03
4.- Generate the authorization.
5.- Set my user "TESTUSER" on the user tab
6.- Save the profile
Then, I login to CRM whit TESTUSER and I see all the leads. I miss something, what could be the problem ?
Thanks for your help

Hi Shaji, Pankaj and Jushan, thanks four your answers.
I still have the same problem, I want to see only my leads that I´am the responsible, after I generated the authorization and assign the role to my user from tcode PFCG and SU01, I logout and login again and no changes, I still see all the leads.
Another test I made, I changed the authorization data and set the values for CRM_ORD_OP: PARTN_FCT , PARTN_FCTT 0008, ACTVT ' (person responsible) and the results was the same, see all the leads.
How works the User Comparisons and how can I check for errors in my pfcg role ?
Thanks for your help.

Doubt about "Business Transaction"

Hello Experts,
On the transaction KE4G, we assign "Business Transaction" to "Characteristic Group". Here goes my question, where does this field "Business Transaction" comes from? it belongs to FI, CO, SD ?? is it a customizable field? a standard one?
Thanks in advance!
Regards.
leandro

Hi,
business transaction is a SAP internal information for each posting, its not customizeable. Based on the source transaction it is added to every line item.
SAP F1 help for this field:
More than one business transaction can be executed in a system
transaction. One business transaction may also be executed in multiple
system transactions.
best regards, Christian

Derived business transactions and TBB1

Dear experts,
My question concerns Money Market derived business transactions.
When I enter position outflows that are not transfer postings, the system generates derived translations that update the position components (proportionate reduction) u2013 DBT_E001/DBT_E002.
These translations are not relevant for posting, but have a status Planned.
The question: is it possible to fix these derived flows during posting of operative business transactions in TBB1?
Right now I can fix them only through TPM18, which is very inconvenient to run separately.
Any help would be appreciated.
Best wishes,
Irina

Hi,
In status control the setting is status of plan and hence the derived transactions will always be generated in planned status and you have to fix them through TPM18.
In order to post it through TBB1 itself, the control setting should have same status option. But check with the business also whether this is not going to have any other effect because this is at the central company code and valuation area level. All derived transactions will have the same status of the operative transactions itself.
Regards,
Ravi

Can anybody help about the conditions in CRM business transaction??

Hi experts,
I'm fresh on CRM and have several questions regarding the conditions in CRM business transactions.
Can you please help?Thanks in advance.
In prciing procedure,we can determin which condition should be involved in item level,
then,how about the conditions in header level??How and where they can be determind?
how the condition value can be calculated?I think they should be the collection of the conditions of the items.
Am I right?
Thanks.

Hello Jerry
Basically you are right, at header level you should see the collection of the conditions of the items. However there are also conditions that can be entered at header level ( header conditions). You can see more information about these conditions in SD documentation:
http://help.sap.com/erp2005_ehp_05/helpdata/EN/dd/561760545a11d1a7020000e829fd11/frameset.htm
See sections:
Header and item conditions
Distribution Between Header and Items
In "Distribution Between Header and Items" you can see how HB00 and RB00 condition types work. If you create your pricing procedure in CRM ( not downloaded from R3) then you can use 0HB0 and 0RB0, which are the CRM counterparts of HB00 and RB00
Best Regards
Luis Rivera

Business Transaction Type for Foreign Trade determination

Hi Gurus,
Can someone explain me the determinations rules for Business Transaction Type for Foreign Trade ? We had this field as mandatory condition in an incompletion procedure for deliveries .
Regards

Hi
These notes will help you
SAP Note 173411 - Incompletion procedures for foreign trade
SAP Note 354222 - Foreign trade data incomplete for domestic business
SAP Note 386484 - Foreign trade: Differentiated use of incompleteness log
SAP Note 118573 - User exits foreign trade data in SD and MM documents
SAP Note 391764 - Foreign trade:Incompleteness procedure in delivery documents
and related notes
Regards
Eduardo

Business transaction control in status schema regarding date determination

Hi all,
is there a business transaction in the status schema that can control the date determination ?
My problem is that the dates are redetermined every time I change status. I can't set the flag "Determine date only once" in the date profile because I wan't the dates to be re-determined when I change the priority. But not when changing the status. How is that controlled ?
Best regards
Annette

Hi Anette,
ITS not possible to control the date determination with standard customizing. Its the event handler CRMV_EVENT that triggers the date determination on change of status. Functions CRM_DATES_RESET_CALENDAR_EC and CRM_DATES_ACTUALDATE_SET_EC are defined for object name STATUS on Event AFTER_CHANGE. You would need to modify this to change the standard functionality.
Hope this helps.
Kind regards,
Vanessa

Business transaction - get info about attached documents

Hello,
I'm looking for some FM to get infos about the documents in the business transaction. I need to know if a folder has been created, if a document has been attached in this folder...
If you also know a FM to create some folders, it is also welcome.
Thanks and Regards,
Frédéric

Dear Frederic,
you can try something like the following code (it checks if a document with the name LOGO is assigned to a Businesspartner and works in a same way for business transactions:
DATA:
 lt_documents TYPE skwf_ios,
 lt_doc_phios TYPE skwf_ios,
 lt_properties TYPE sdokproptys.
DATA:
 ls_sibflporb TYPE sibflporb.
FIELD-SYMBOLS:
 <lfs_document> TYPE skwf_io,
 <lfs_phio> TYPE skwf_io.
* get all documents to the businesspartner
ls_sibflporb-instid = lv_partner_guid.
ls_sibflporb-typeid = 'BUS1006'. "#EC NO-TEXT .
ls_sibflporb-catid = 'BO'. "#EC NO-TEXT.
CALL FUNCTION 'SKWG_OLS_BO_LINKS_GET'
 EXPORTING
 BUSINESS_OBJECT = ls_sibflporb
* RELATION = 'WCM_LINK'
* CSPC = ' '
 TABLES
 IOS = lt_documents.
* try to find the right document (name = LOGO)
LOOP AT lt_documents ASSIGNING <lfs_document>.
 REFRESH lt_properties.
* Eigenschaften lesen
 CALL FUNCTION 'SKWF_IO_PROPERTIES_GET'
 EXPORTING
 IO = <lfs_document>
 TABLES
* PROPERTIES_REQUEST =
 PROPERTIES_RESULT = lt_properties.
* Property "KW_RELATIVE_URL" have to be LOGO!!! READ TABLE lt_properties WITH KEY name = 'KW_RELATIVE_URL'
 value = 'LOGO'
 TRANSPORTING NO FIELDS.
 CHECK sy-subrc EQ 0.
* do something......
 ENDLOOP.
Regards,
André

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.

Questions about Territory determination in Business transactions in CRM 7.0

Similar Messages

Maybe you are looking for