Skip to Content
author's profile photo Former Member
Former Member

Problem with ORG Determination in Transactions

I am having an issue with ORG determination in Business Transactions

The Organization area is not being populated as required.

I want to pull in the org data from the User (Org data set in Sales Area section of the BP), all users have the same org data, when running the transaction this is not working, this used to work ok but no longer does??

Settings in org data profile is set to '14000146 - Org. Unit Using Transaction Type', this brings back two errors:

1 - No organizational units found

2 - No organizational unit could be selected

I have tried using the 10000194 - UserOrgUnit but this causes a pricing determination error relating to config

any ideas anyone??

regards

Barry

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Apr 25, 2010 at 10:58 PM

    Can you check if the Obj permitted in determination for sales scenario in Tcode - PPOSA_CRM is activated or not. If not please activate and try.

    Hope this helps.

    Edited by: Chandrakant A on Apr 26, 2010 12:59 AM

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Apr 26, 2010 at 04:21 AM

    Hello Barry,

    To use rule 14000146, you need to add the used transaction type as an attribute of the org. unit that you want it to be determined.

    To do this, please execute t-cd ppoma_crm, open your org. unit, go to the [Attributes] tab, add the transaction type into the 'Transaction Type' attibute, then check on 'Obj. permitted in determination' save.

    Wiith rule 10000194 you got the org. unit determined. For the pricing error, I think it might be related to the pricing procedure determination. If yes, please check your IMG activity:

    SPRO

    - CRM

    - Basic Functions

    - Pricing

    - Pricing in the Business Transaction

    - Determine Pricing Procedures

    Here, the Sales organization, Dis. Channel, Division are the org. data determined in the transaction; the Doc. Pricing Procedure is the one defined in the transaction type (IMG activity: Define Transaction Types->Assignment of Business Transaction Categories-> BUS2000115 -> Customizing header -> field 'Doc. Pric.Proc.'); the Cust. Pricing Procedure is taken from the sold-to party's BP master sales area data (in the billing) tab.

    Hope the information could be helpful.

    Best regards,

    Maggie

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Thanks for your replies:

      Chandrakant

      Obj permitted is ticket(activated) throughout the sales org

      Maggie

      When I try to add the Transaction Type i get a message 'A selection cannot be made for this line'...??

      I have checked the pricing proc and all looks well,

      still having the issue...

      regards

      Barry

  • author's profile photo Former Member
    Former Member
    Posted on Oct 12, 2010 at 01:30 PM

    Closed as no responce

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.