Account Assignment Features through Transaction PP01

Hi All,
Using PP01 Tansaction i try to do the Account Assignment feature for a Org. unit.  When i enter both company code and personal area it is giving an error message as "Company code 0001 has been set in the structure above"
Let me know how can i avoid this.
thanks
-Suresh

Hi,
<b>Inheritance:</b> Same features are assigned/ followed automatically by the hierarchy.
<b>SAP Definition:</b>
This entry enables you to determine that account assignment features(controlling area, company code, and business area) are passed from organizational units to lower-level positions.
In the standard system, inheritance is deactivated (value ' ').
If you want to activate inheritance, enter the value 'X'.
<b>Default System setting:
Group     Sem.abbr     Value abbr     Description</b>
PPOM     INHIC          X          'X': PPOM: Obligatory Inheritance of Company Code
PPOM     INHIH          X          'X': PPOM: Obligatory Inheritance of Contr. Area
PPOM     INHS                    Inheritance of acc. ***. features by positions
1.     For Company code: PPOM – INHIC
2.     For Controlling area: PPOM – INHIH
3.     For Inheritance: PPOM – INHS
<b>NOTE: ‘X’ Activation key for all the Integrations</b>

Similar Messages

  • What is meant by Account Assignment Feature.

    Hi
    Pls tell me about account assignment feature.

    Hi there,
    Payroll result transferred to FICO, is account assignment for employee
    PPMOD: set employee subgroup grouping for account determination based on employee characteristics in payroll result (work center , basic pay, structure WPBP)
    Report:RPCIPE00,
    Posting to accounting , create posting run
    u20221ST Symbolic account are created
    u2022Symbolic accounts  constitutes the links between wage type in payroll and G/L account in FICO
    u2022Unlimited number of wage type can be pointed to same symbolic account
    u2022 A wage type can be also pointed to more than one G/L Account
    u2022The important point is to send the wage type
    Debit to one , and credit to other in order not to affect the overall balance of the account
    u2022PPMOD features determine to which G/L account the payroll of personnel will be transferred based on their master data (eg:ES grouping =1, send to u2026u2026u2026account )
    u2022PPMOD 
    u2022In the structure part of PPMOD, it is possible to refer to which  master data of employee can be used for restriction
    u2022     HRPAYROLAMERICAUSASUBSEQUENT ACTIVITIESPERPAYROLL PERIOD
    EVALUATIONPOSTING TO ACCOUNTING
    Thanks!

  • Account assignment through material group?

    Hi All,
    Can anybody suggest me, How to done the account assignment config. through Material group.
    And what all the significance of material group. i.e. in which scenarios material group comes in the picture?

    hi,
    material group comes in to picture for,
    1.Manatain Delivery Tolerances
    2.Procurement Analysis by material groups âu20ACu201C most of the standard reports support material groups
    3.Vendor Evaluations based of Material Groups
    4.Vendor Information Record âu20ACu201C material groups âu20ACu201C if you have a long-term relationship with your Vendor for a particular Product , you can maintain the planned delivery time , pricing , quantity, discounts for the vendor
    5) Automatic account assignment determination
    6) Release Strategy
    7) Reference for the definition of purchasing group etc..
    regards

  • Org Mangt: Inheritance of Account Assignment

    Hi All,
    The issue I am facing is, when I create a position under an organization through transaction PPOME, it is not inheriting the account details (company code, pers. area, pers. subarea) from org unit. What is surprising in this is when I create a back dated entry, inheritance works just fine. Anyone faced a similar issue?
    Thanks in advance!!!
    Regards,
    Bhaskar

    Hi,
    do you have in your system note 1591799 installed?. This note have created a side effect that is corrected with note::
    1599180: Transaction PPOME/account assignment features/inheritance
    Take a look at the following note, which have good explanation about the process:
    1613376 PPOME: Inheritance and display of account assignment chars.
    Regards,
    Ana

  • OM Account Assignment - Inheritance Principle

    Hi
    We are all ware that the Switch PPOM INHS when off, turns off the account assignemnt inhertitance from Org Unit to Position.
    But... How can we turn off the Org Unit to Org Unit account assignment inheritance in ECC 6.0
    To put it in simpler terms, I do not want the subordinate org unit to inherit the account assignment feature of the superior org unit. And can this be seen and/or done through PPOME?
    Thanks in advance for your inputs
    Shyam

    Hi Shyam,
    I have worked on the Issue that you have quoted. Please find below my observations:
    Org Unit - Org Unit Relationship in PPOME:
    CA01----
    CA02
        |----CA11
        |----US01                                     
    Structure: Two Org Units (CA01 and CA02 at the same level has got the Same Account Assignment Feature say
        Co. Code: CAA1
        PA:          CA00
        PSA:        CACA
    Fundamentally, Rule of Inheritance states Unless and until you EXPLICITLY change the values in the Subordinate Object, it will inherit the values from the Root Object or Parent object.
    Therefore, CA11 and US01 Should inherit the Values maintained in CA01. However, since you have explicitly changed the Values for US01 to
        Co Code: US00
        PA:         US01
        PSA:       USUS,
    the inheritance will NOT take place. For CA11, the inheritance follows.
    Your Switch for PPOM INHS is set to active.
    Coming to your Scenario 1:
    When I move CA11 as a Subordinate unit of US01 the account assignment features of US01 are inherited by CA11 (This should not happen);
    It will happen because, in the first place, you have Just caused an Inheritance to happen from CA01 to CA11 which is default and therefore not Explicit. Therefore, when you further move this org Unit CA11 to US01; it will follow the same process and inherit the values of US01.
    Scenario 2:
    Whereas when I move CA02 as a subordinate unit of US01 the account assignment feaures of US01 are NOT inherited by CA02 (This is correct).
    This is because you created the Org Unit with Account Assignment Features and Saved it (making it as explicit unit) and even if you move this unit under US01 or any other Org Unit it will NOT inherit values of the then PARENT unit. Moreover, if you relate any further org unit/position to CA02 (after you have related CA02 to US01); all the subordinate units/position will inherit the account assignment feature of CA02; which is quite valid.
    To my knowledge, to solve this, you will have to mandatorily click the Replace buttons available and set it to the requisites.
    Considering that you are using PPOME, it would be a case of few of the org units.. and therefore it wouldnt be a difficult task to do.
    Hope this helps.
    Best Regards,
    Kumarpal Jain.

  • Profit center and Partner profit center assignment in TM transaction

    Dear Experts,
    I am very new on TRM, could you tell me how you define profit center and partner profit center for FI posting pass from TRM? I did not see there is field for PC or PPC on any of TM transaction.
    Appriciate your help.
    thanks
    CK

    Hi,
    For postings from treasury you can assign default profit center and business area (also segment from EH3) to account assignment reference.  The basic idea being that you generally manage all similar transactions with same account assignment reference through a same organization unit like profit center.  You do this assignment in TRM -- General Settings -- Accounting -- Link to other Accounting Components -- Assign additional account assignments.
    However in case you want to have a different profit center derived in a different way than through account assignment reference, you could use a custom logic and derive it using the BAdI TPM_ACCIF_TRAC.
    Regards,
    Ravi

  • SAP Treasury GL Account Assignment

    Hi,
    i have done following settings
    1 GL Account assigned for share transactions including taxation, charges, commission, brokerage services, advisory services etc.
    Is there any need of number of GL Accounts assignment for every transactions like taxation, brokerage services, advisory services, etc
    In case of Key Date Valuation, what type of Problems  faced
    please advice me
    with regards
    raju

    Dear Raju,
    Answering your 1st question, There is no straight rule for number of GL, Its based on organization requirement.
    Most of the organization want to account expenses on individual account for reporting purpose. Hence we need to assign different GL, How ever there is no straight rule for the same.
    Answering your 2nd question, For valuation, You shall follow below steps, Incase all the customization is correct the valuation will happen without any error.
    Create contract(FTR_CREATE)
    Settle the contract(FTR_EDIT)
    Post all valued cash flows(TBB1)
    Save NPV         (TPM60)
    Carrying out valuation run(TPM1)
    Let me know if you need any more inputs.
    Regards,
    Jain

  • Edit OM infotype 1008 (Acct. Assignment Features)

    Hi,
    I have added  OM IT 1008 to PPOME.
    But somehow, the option to edit, create , delete it, is missing in PPOME.
    do you know how to fix this?
    Regards
    KP

    Dear KP,
    You can use the T-Code PO13 to maintain the infotype 1008 i.e. account assignment features.
    Regards,
    Ritu

  • About account assignment category

    Hi, I have a question about account assignment category.I hope someone give me the answer , and I would appreciate it.
        If there is a final product A, and the planning strategy for A is 20(MTO), the procurement type of A is F(external procurement) at the view mrp2 in the material master datas.
    step1: I creat a sales order.
    step2: run MRP for A.
    step3: transfer the purchase requistion into a purchase order,and the field of acc.***.cat. in the purchase order will be filled out M automatically, because the acc.***.cat. in the planning strategy 20(MTO) is set with E.
        Well, the purchase order is created, what is the relationship between the sales order and the purchase order? What will be happened about costing between the SO and the PO?
        If I delete the E, I make the PO become a standard PO, what is difference between standard PO and the PO including E?
    Best Regards
    Bob

    Hi,
    Definition: Account Assignment Category: - A key indicating whether an item is to be assigned to an auxiliary account (such as a cost center).
    The account assignment category determines which account assignment details are required for the item (for example, cost center or account number).
    Generally used Account Assignment Categories are Cost Center (K) in case of Miscellaneous Purchases, Assets (A) in Capital Goods Purchases, etc...
    You can configure Account Assignment Category in Transaction OME9 OR you can go with following path;
    SPRO > MM > Purchasing > Account Assignment > Maintain Account Assignment Categories
    Her you have to perform following Activities;
    1.  Check the attributes of the account assignment categories
    2.  Maintain the account assignment categories to suit your requirements

  • Account assignment references

    HI Gurus,
    I am battling to set up account assignment references in Transaction Manager. As a result, I am unamble to post to FI for my MM transactions. Even when i go to my update types, they do not have any G/L accounts assigned to them. Can anyone assit me with a methodical way to go about this?.
    Regards

    Hi,
    In the accounting node in Transaction Manager, go to Link to other accounting components.
    First define your account reference name in the accounting component.
    Then define a derivation rule.  Here read the documentation.  The way should be that your account assignment reference should be automatically assigned to the money market transaction based on your product type and probably currency.
    Then in the Define account determination node -- define a posting specification and assign it to your update type.  Define an account symbol and specify what kind of an account it is.  In posting specification, specify the account symbol  for debit and credit entries.
    Then assign your account symbol a G/L account based on the valuation area and account assignment reference.
    Regards,
    Ravi

  • About Account assignment templates

    Dear Experts,
            When user use FV70 Tree on button ,they can see all users Account assignment templates list,how to control use only see themselves  account assignment templates,current user can not see another users account assignment templates?
            Looking forward to your reply.
    Best Regards,
    Merry

    Hi,
    Definition: Account Assignment Category: - A key indicating whether an item is to be assigned to an auxiliary account (such as a cost center).
    The account assignment category determines which account assignment details are required for the item (for example, cost center or account number).
    Generally used Account Assignment Categories are Cost Center (K) in case of Miscellaneous Purchases, Assets (A) in Capital Goods Purchases, etc...
    You can configure Account Assignment Category in Transaction OME9 OR you can go with following path;
    SPRO > MM > Purchasing > Account Assignment > Maintain Account Assignment Categories
    Her you have to perform following Activities;
    1.  Check the attributes of the account assignment categories
    2.  Maintain the account assignment categories to suit your requirements

  • No entry for account key 1002 in HRA transaction key in Account assignment

    Dear sap-gurus,
    the following problem occured. When posting a document (s-modelling), system displayed an error that there is no entry for account key 1002 in HRA transcation key in SPRO Account assignment.
    The document's size is very big, it considers many lime items in it.  May be this happened because of this?
    In F1 for SPRO Account assignment we have:
    In this step, you assign a document split account to an account key. This is a clearing acount (Transaction HRA) in Accounting.
    For various reasons, payroll data that is formatted for posting to accounting must be split into several documents per posting run. In Human Resources (HR), key 1001 is used for the breakdown of documents. A breakdown occurs if:
    There are several company codes
    There are different posting dates
    There are postings to G/L accounts, customer accounts, vendor accounts
    This is specified in the step Create Posting Variants (for example, document breakdown for expenses and payables)
    The document split account that is stored under the key 1001 is also used to clear the balance within a G/L account document for each business area.
    An additional split may be required depending on the size of the document in Financial Accounting. In this case, the clearing account specified under account key 1002 in transaction HRA, is used as the document split account.
    Further notes
    To avoid problems in current operations, it is advisable to set up a document split account even if a document breakdown is not necessary. In this way, you can avoid having to set up the system at short notice if changes are made to the settings or if there is an increased number of postings, or if cross-company code transactions occur.
    We have an entry 1001 and a clearing account for postings between several company codes. What are we supposed to do? How to avoid this error and post the documents to FI? Please, help!
    Best regards,
    Eldar

    Hello,
    How did you resolve this issue? Any inputs anyone.
    John

  • Transaction ME23N; Create purchase order- Account assignment tab

    Hello , do you know in which table the info for account assignment for a purchase order is kept?
    e.g just like EKBE is used for Purchase order history.
    thx.

    Table Description u2013 All Tables: Purchasing
    EBAN  Purchase Requisition 
    EBKN  Purchase Requisition Account Assignment 
    EBUB  Index for Stock Transport Requisitions for Materi
    EINA  Purchasing Info Record: General Data 
    EINE  Purchasing Info Record: Purchasing Organization D
    EIPA  Order Price History: Info Record 
    EKAB  Release Documentation 
    EKAN  Vendor Address: Purchasing Document 
    EKBE  History per Purchasing Document 
    EKBEH  Removed PO History Records 
    EKBZ  History per Purchasing Document: Delivery Costs 
    EKBZH  History per Purchasing Document: Delivery Costs 
    EKEH  Scheduling Agreement Release Documentation 
    EKEK  Header Data for Scheduling Agreement Releases 
    EKES  Vendor Confirmations 
    EKET  Scheduling Agreement Schedule Lines 
    EKETH  Scheduling Agreement Schedules: History Tables 
    EKKI  Purchasing Condition Index 
    EKKN  Account Assignment in Purchasing Document 
    EKKO  Purchasing Document Header 
    EKPA  Partner Roles in Purchasing 
    EKPB  "Material Provided" Item in Purchasing Document 
    EKPO  Purchasing Document Item 
    EKPV  Shipping Specific Data on Stock Tfr. for Purch. D 
    EKRS  ERS Procedure: Goods (Merchandise) Movements to b 
    EKUB  Index for Stock Transport Orders for Material 
    EORD  Purchasing Source List 
    EQUK  Quota File: Header 
    EQUP  Quota File: Item 
    T- Tables
    T024  Purchasing Groups 
    T024E  Purchasing Organizations 
    T024W  Valid Purchasing Organizations for Plant 
    T024Z  Purchasing Organizations 
    T027A  Shipping Instructions, Purchasing 
    T027B  Texts: Shipping Instructions 
    T027C  Codes for Compliance with Shipping Instructions 
    T027D  Compliance with Shipping Instructions: Texts 
    T069  Certificate Categories 
    T069Q  Control Data for Source Determination and Checkin 
    T069T  Certificate Categories: Text Description 
    T160  SAP Transaction Control, Purchasing 
    T160B  SAP Transaction Control, List Displays, Purchasin 
    T160C  SAP Transaction Control for List Displays in CALL 
    T160D  Function Authorizations: Purchase Order 
    T160E  Function Authorizations: Purchasing: Descriptions
    T160I  Control of Intrastat Reports 
    T160J  Text Table for Intrastat Reports 
    T160L  Scope of Purchasing Lists 
    T160M  Message Control: Purchasing (System Messages) 
    T160O  Description of Scope of List 
    T160P  Entities Table Routines 
    T160Q  Scope of List: Buyeru2019s Negotiation Sheet: Routine
    T160R  Routines for Buyeru2019s Negotiation Sheet 
    T160S  Selection Parameters for Purchasing Lists 
    T160T  Description of Selection Parameters 
    T160V  Default Values for Purchasing 
    T160W  Description for Default Values for Purchasing Ope
    T160X  Scope of List: Buyeru2019s Negotiation Sheet 
    T160Y  Scope of List: Buyeru2019s Negotiation Sheet: Descrip
    T161  Purchasing Document Types 
    T161A  Linkage of Requisition Doc. Type to Purchasing Do
    T161B  Default Business Transaction Type for Import 
    T161E  Release Codes 
    T161F  Release Point Assignment for Purchase Requisition
    T161G  Release Prerequisite, Purchase Requisition 
    T161H  Fields for Release Procedure, Purchase Requisitio
    T161I  Determination of Release Strategy 
    T161M  FineTuned Control: Message Types 
    T161N  Message Determination Schemas: Assignment 
    T161P  Check of Document Type, Document Category, Item C
    T161R  REORG Control, Purchasing 
    T161S  Release Indicator, Purchase Requisition 
    T161T  Texts for Purchasing Document Types 
    T161U  Texts for Release Indicator 
    T161V  Shipping Specific Data for Stock Tfr. for Purch. 
    T161W  Order Types for Stock Transfer 
    T161Z  Additional Checks for Outline Agreements on Reorg
    T162  Field Selection, Purchasing Document 
    T162K  Field Selection, Account Assignment Fields, Purch
    T162T  Description of Field Selection Reference Key 
    T162X  Description of Field Groups from T162/T162K 
    T162Y  Groups: Field Selection 
    T163  Item Categories in Purchasing Document 
    T163A  Check Item Category/Account Assignment Category 
    T163B  Purchase Order History Categories 
    T163C  Texts for Purchase Order History Categories 
    T163D  Assignment Internal/External Confirmation Categor
    T163E  Confirmation Categories 
    T163F  Confirmation Categories: Descriptions 
    T163G  Confirmation Control 
    T163I  Texts for Account Assignment Categories 
    T163K  Account Assignment Categories in Purchasing Docum
    T163KS  Assignment of Tax Indicator to Account Assignment
    T163L  Confirmation Control Keys 
    T163M  Confirmation Control Keys: Description 
    T163P  Release Creation Profile 
    T163S  Description for Release Creation Profile 
    T163X  "Zombie" T163X 
    T163Y  Texts for Item Categories 
    T165K  Copying Options: Header Texts 
    T165P  Copying Options: Item texts 
    T166A  Supplement Text in Purchasing Document Printouts 
    T166C  Print Relevant Purchasing Document Changes 
    T166K  Header Texts in Purchasing Document Printouts 
    T166P  Item Texts in Purchasing Document Printouts 
    T166T  Change Texts in Purchasing Document Printouts 
    T166U  Headings in Purchasing Document Printout 
    T167  Number Range Management for Purchasing Master Dat 
    T167T  Transaction Description 
    T168  Screen Control, Purchasing 
    T168F  Function Codes, Purchasing 
    T168T  Screen Titles 
    T16FB  Release Indicators: Purchasing Document 
    T16FC  Release Codes 
    T16FD  Description of Release Codes 
    T16FE  Descriptions of Release Indicators: Purchasing Do 
    T16FG  Release Groups 
    T16FH  Descriptions of Release Groups 
    T16FK  Release Statuses 
    T16FS  Release Strategies

  • Transaction type + account assignment

    Helllo!!
    How could I assign account that I need, to new transaction type that I have created?
    For example, I have created tr.type XXX and would like postings with this tr. type to acconts Debit44444-Credit777777 and not to Debit 111111-Credit22222 as it is by default. In AO90 for this class I have accounts 444444 and 777777, not 11111/22222.

    You cannot assign GL accounts to the T-types. From AO90 account determination it will take the GL accounts based on the transaction processed and T-type determines what kinda transaction it is i.e. acquisition, retirement, etc.

  • G/L Account assignement to Transaction Event Keys

    Hi Friends,
    Please let me know where exactly in customization we assign the G/L accounts to Transaction event keys.
    For example
    For transaction event key AUF  ( Order settlement) which G/L account is going to it and how ?
    Where is the configuration setting ?
    Helpfull answers are rewarded.
    Thanks & Best Regards
    Giri

    Hi,
    Assign GL Account in OBYC for T/E Key GBB, here you have to assign GL A/c for the combination of Valuation Grouping Code 0001, Valuation Class (from Material Master) and Valuation Modifier AUF
    Here assign Inventory Change Account, it gets triggered at the time of Order Settlement (in KO88) if GL Account for AUA is not maintained.
    Note: - AUF is used for goods receipts for orders (without account assignment) and for order settlement if AUA is not maintained

Maybe you are looking for