Unable to create a sales document

Hi frns,
while creating sales document (order) an error poping up saying No customer master record exists for Sold to Party.. Pls advise how to solve da above
regards,
kk

There is a possibility that a Customer Master record is not created, or if it is created, it may not be created in the required Sales Area. Please create Customer Master Data in XD01 & after that create Sales Order. It certainly shoule create Sales order. Also check your configuration for SD:
SD Configuration:
Enterprise Structure:
1. Maintaining Sales Organization
Sales Organization is an organizational unit responsible for the sale of certain products or services.
IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check Sales organization
2. Assigning Sales Organization to Company Code
This assignment ensures all the sales made through this Sales Organization are accounted for in the assigned Company Code (Company Code is created by FI Consultant).
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign Sales Organziation to Company Code
3. Maintaining Distribution Channel
Distribution Channel is the way, in which Products or Services reach Customers.
IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check distribution channel
4. Assigning Distribution Channel to Sales Organization
This assignment ensures, a Sales Organization can supply Materials to Customers through this Distribution Channel.
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution > Assign distribution channel to sales organization
5. Maintaining Division
Division is a way of grouping materials, products, or services.
IMG -> Enterprise Structure -> Definition -> Logistics - General -> Define, copy, delete, check division
6. Assigning Division to Sales Organization
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign division to sales organization
7. Setting up Sales Area
All the sales are made from a particular sales Area. For creating a Sales Order Sales Area is compulsory.
IMG ->Enterprise Structure -> Assignment -> Sales and Distribution -> Set up sales area
8. Assigning Sales Organization- Distribution Channel- Plant
Plant is created ny MM Consultant.
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign sales organization - distribution channel - plant
9. Define Shipping Points
Shipping Point is the Organizational element, which is responsible for shipping the Materials to the Customers.
IMG -> Enterprise Structure -> Definition -> Logistics Execution -> Define, copy, delete, check shipping point
10 Assigning Shipping Point to Plant
This assignment ensures that goods from different Plant can be dispatched from different Shipping Points.
IMG -> Enterprise Structure -> Assignment -> Logistics Execution -> Assign shipping point to plant
Note: Ensure to do the undermentioned configuration also though it is not in Customizing node of Enterprise Structure.
11. Defining Common Distribution Channels for Master Data
Use
The purpose of this activity is to define distribution channels which have common master data..
Procedure
Access the activity using one of the following navigation options:
IMG Menu -> Sales and Distribution -> Master Data -> Define Common Distribution Channels
Transaction Code: VOR1
12. Defining Common Divisions for Master DataUse
The purpose of this activity is to define distribution channels which have common master data..
Procedure
Access the activity using one of the following navigation options:
IMG Menu -> Sales and Distribution -> Master Data -> Define Common Division
Transaction Code: VOR2
Pricing Procedure
In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
In SD, the steps to configure Pricing procedure are as under:
Step 1:
Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
5. Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.
Normal Sales Order Cycle:-
Step 1: Sales Document Type
IMG > Sales and Distribution > Sales > Sales Documents >
Sales Document Header:
1. Sales Document Type:The sales document types represent the different business transactions, such as Inquiry, Quotation, Sales Order, etc. To create new sales order type, always copy as with reference to similar sales order. If possible use standard sales order.
2. Define Number Ranges For Sales Documents: Maintain number range with discussion with core team.
3. Assign Sales Area To Sales Document Types:
A. Combine sales organizations / Combine distribution channels / Combine divisions: Ensure to maintain these, else Sales Order creation will give error.
B. Assign sales order types permitted for sales areas: Assign only required Sales Order Types to required Sales Area. This will minimize selection of Sales Order Type as per sales area.
Sales Document Item:
1. Define Item Categories: If possible use Standard Item Category. Incase if required to create new, copy as from standard & maintain New.
2. Assign Item Categories: If possible, use standard. Formula for deriving item category: Sales Document Type + Item Category Group + Usage + Higher Level Item Category = Item Category
Schedule Line:
1. Define Schedule Line Categories: If possible use Standard Schedule Lines. Incase if required to create new, copy as from standard & maintain New.
2. Assign Schedule Line Categories: If possible, use standard. Formula for deriving Schedule Line: Item Category + MRP Type / No MRP Type.
Step 2:
IMG > Logistic Execution > Shipping > Deliveries >
1. Define Delivery Types: If possible use Standard Delivery Type. Incase if required to create new, copy as from standard & maintain New.
2. Define Item Categories for Deliveries: If possible use Standard Item Categories for Delivery Type. Incase if required to create new, copy as from standard & maintain New.
3. Define Number Ranges for Deliveries: Ensure to maintain number range.
Step 3:
IMG > Sales and Distribution > Billing >
1. Define Billing Types: If possible use Standard Billing Type. Incase if required to create new, copy as from standard & maintain New.
2. Define Number Range For Billing Documents: Ensure to maintain number range.
3. Maintain Copying Control For Billing Documents: Maintain relevant copy controls such as Sales Order to Billing, Deliver to Billing, etc.
The configuration differs from scenario to scenario & requirement of the client.
Regards,
Rajesh Banka
Reward point if useful.

Similar Messages

  • Unable to create the sales doc with ref to quotation

    Hi,
    I am unable to create a sales order with ref to quotation, messege is "Create sales document" not allowed (User Status
    MKT, object VB0006000017000000)".
    how please advice me
    chandu

    Dear Chandu,
    In Copying Control from QT to OR:
    Kindly set the Copying Requirements: 301 for all Item
    And Copying Requirements: 501 for all schedule lines and check if the sales order is created now.
    Regards,
    Ashu

  • Problem in creating a sales document

    Hi,,
    I am creating a sales document programatically by the FM BAPI_SALESDOCU_CREATEFROMDATA1 for tht i have desigend ny selection screen in tht my requirement is i will not give item category for tht i have to quiery for given material and for given plant i have to fetch itcat plz help me in writing this quiery
    vbap table is not coreect as it will store data after complettion of sales document
    but here i want quiery to create a sales document it self
    i have seen in transaction VA01 ity is getting data from t184 for itcat plz help me in writing this quiery
    for good answer i will reward points

    You can use the t.code SHD0, choose your transaction variant here, further choose your screen variant.
    Next select your screen variant and in the Menu bar select Variant> change with processing>Make repairs in foreign namespaces only if they are urgent> Continue(Enter)>again 'enter'>Object can only be created in SAP package>continue(enter)> Exit and save >This variant contains other screens, adopt these as well?>enter>enter> scroll down to the entry make the necessary changes and save.
    The system will prompt to assign a package and request enter the necessary values.
    Your issue is sorted!!
    And further to your query for minimum price PMIN refer to my answer, you will not have to maintain any condition record or the price entered here does not reflect in any other document.
    Regards,
    PATHIK

  • Creating a sales document using BAPI in web dynpro by uploading a file

    Hi ALL,
    Can some one help me how to create a sales document using  BAPI by uploading a file as input...Can someone  provide me a sample program....
    Thanks n Regards,
    Praveenn.
    Edited by: praveenn on Aug 23, 2011 12:42 PM

    Hi Sri,
    Thx for the response...
    Here is the code that i followed for creating a BAPI_SALESORDER_CREATE1 by uploading a text file as input.
    Just create a Attribute  in the VIEW CONTEXT of type String.
    method ONACTIONCREATE_SO .
    types : Begin of ty_data,
             sales_org  type vkorg,
             doc_type   type AUART,
             DISTR_CHAN type VTWEG,
             DIVISION   type spart,
             material   type matnr,
             partn_role type PARVW,
             PARTN_NUMB type kunnr,
           end of ty_data.
      DATA  :it_table TYPE  TABLE OF ty_data,
             i_data   TYPE  TABLE OF string,
             l_string TYPE string,
             wa_table TYPE ty_Data,
             l_xstring TYPE xstring,
             fields TYPE string_table,
             lv_field TYPE string.
    DATA: wa_order_header_in TYPE BAPISDHD1,
          it_order_items_in  TYPE TABLE OF BAPISDITM,
          wa_order_items_in  TYPE BAPISDITM,
          it_order_partners  TYPE TABLE OF BAPIPARNR,
          wa_order_partners  TYPE BAPIPARNR,
          it_return TYPE TABLE OF BAPIRET2,
          wa_return TYPE BAPIRET2.
    DATA : sales_doc type bapivbeln-vbeln.
    DATA:
       node_zfinal_node  TYPE REF TO if_wd_context_node,
       elem_zfinal_node  TYPE REF TO if_wd_context_element,
       stru_zfinal_node  TYPE if_main_view=>element_zfinal_node .
    get single attribute
      wd_context->get_attribute(
      EXPORTING
      name =  'DATASOURCE'
      IMPORTING
      value = l_xstring ).
      CALL FUNCTION 'HR_KR_XSTRING_TO_STRING'
        EXPORTING
          in_xstring = l_xstring
        IMPORTING
          out_string = l_string.
    SPLIT l_string  AT cl_abap_char_utilities=>newline INTO TABLE i_data.
      LOOP AT i_data INTO l_string.
       SPLIT l_string AT cl_abap_char_utilities=>horizontal_tab INTO TABLE fields.
        READ TABLE fields INTO lv_field INDEX 1.
        wa_table-sales_org = lv_field.
        READ TABLE fields INTO lv_field INDEX 2.
        wa_table-doc_type = lv_field.
        READ TABLE fields INTO lv_field INDEX 3.
        wa_table-DISTR_CHAN = lv_field.
        READ TABLE fields INTO lv_field INDEX 4.
        wa_table-DIVISION = lv_field.
        READ TABLE fields INTO lv_field INDEX 5.
        wa_table-material  = lv_field.
        READ TABLE fields INTO lv_field INDEX 6.
        wa_table-partn_role  = lv_field.
        READ TABLE fields INTO lv_field INDEX 7.
        wa_table-partn_numb  = lv_field.
    APPEND wa_table TO it_table.
      ENDLOOP.
    loop at it_table into wa_table.
    clear : wa_order_header_in.
    wa_order_header_in-sales_org   = wa_table-sales_org.
    wa_order_header_in-doc_type    = wa_table-doc_type.
    wa_order_header_in-distr_chan  = wa_table-distr_chan.
    wa_order_header_in-division    = wa_table-division.
    clear : wa_order_items_in.
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
      EXPORTING
        input         = wa_table-material
    IMPORTING
       OUTPUT        = wa_order_items_in-material.
    *wa_order_items_in-req_qty  = wa_table-req_qty.
    append wa_order_items_in to it_order_items_in.
    clear : wa_order_partners.
    wa_order_partners-partn_role = wa_table-partn_role.
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
      EXPORTING
        input         = wa_table-partn_numb
    IMPORTING
       OUTPUT        = wa_order_partners-partn_numb
    *wa_order_partners-partn_numb = wa_table-partn_numb.
    append wa_order_partners to it_order_partners.
    endloop.
    CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
      EXPORTING
      SALESDOCUMENTIN               =
        order_header_in               = wa_order_header_in
      ORDER_HEADER_INX              =
      SENDER                        =
      BINARY_RELATIONSHIPTYPE       =
      INT_NUMBER_ASSIGNMENT         =
      BEHAVE_WHEN_ERROR             =
      LOGIC_SWITCH                  =
      TESTRUN                       =
      CONVERT                       = ' '
    IMPORTING
       SALESDOCUMENT                 = sales_doc
      tables
       RETURN                        = it_return
       ORDER_ITEMS_IN                = it_order_items_in
      ORDER_ITEMS_INX               =
        order_partners                = it_order_partners.
      ORDER_SCHEDULES_IN            =
    get message manager
    DATA: l_current_controller TYPE REF TO if_wd_controller,
           l_message_manager    TYPE REF TO if_wd_message_manager.
           l_current_controller ?= wd_this->wd_get_api( ).
    DATA:  v_message_text TYPE string.
    When Sales Order is created commit the data
    IF NOT sales_doc IS INITIAL.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
       EXPORTING wait = 'X'.
      CONCATENATE 'Sales Document' sales_doc 'has been created.' INTO v_message_text SEPARATED BY space.
    Report Success message
      CALL METHOD l_message_manager->report_success
      EXPORTING
      message_text = v_message_text.
      ELSE.
      v_message_text = 'Error Creating Sales Order'.
    Report Error message
    CALL METHOD l_message_manager->report_error_message
    EXPORTING
    message_text = v_message_text.
    ENDIF.
    endmethod.
    Edited by: praveenn on Aug 30, 2011 2:41 PM

  • Unable to assign new sales document type to sales area.

    Hi,
    I had created new sales document type. While I assigning to sales area it showing error " Define <XXX/XX/XX > first as a general sales area." I had already created sales area in enterprise structure. I had configured Combine sales org, dist channel & division also. Kindly help me on this.
    Regards
    Nagendra

    Hi,
    I hope you have maintained following Settings:
    SPRO --> IMG --> Enterprise Structure --> Definition --> Sales and Distribution --> Define, copy, delete, check Sales Org
    SPRO --> IMG --> Enterprise Structure --> Definition --> Sales and Distribution --> Define, copy, delete, check Distribution Channel
    SPRO --> IMG --> Enterprise Structure --> Definition --> Logistics - General --> Define, copy, delete, check Distribution Channel
    SPRO --> IMG --> Enterprise Structure --> Definition --> Logistics - General --> Define, copy, delete, check Plant (In case)
    SPRO --> IMG --> Enterprise Structure --> Assignment --> Sales and Distribution --> Assign Sales Org. to Company Code
    SPRO --> IMG --> Enterprise Structure --> Assignment --> Sales and Distribution --> Assign Dist. Channel to Sales Org.
    SPRO --> IMG --> Enterprise Structure --> Assignment --> Sales and Distribution --> Assign Divsion to Sales Org.
    SPRO --> IMG --> Enterprise Structure --> Assignment --> Sales and Distribution --> Set up Sales Area
    SPRO --> IMG --> Enterprise Structure --> Assignment --> Sales and Distribution --> Assign Sales Org.-Dist. Channel-Plant
    SPRO --> IMG --> Sales and Distribution --> Master Data --> Define Common Dist. Channel
    SPRO --> IMG --> Sales and Distribution --> Master Data --> Define Common Division
    SPRO --> IMG --> Sales and Distribution Channel --> Sales Document Header --> Define Sales Doc. Type
    SPRO --> IMG --> Sales and Distribution Channel --> Sales Document Header --> Define No. range Sales Doc.
    SPRO --> IMG --> Sales and Distribution Channel --> Sales Document Header --> Assign Sales Area to Sales Doc. type
    Best Regards,
    Amit

  • When copying pic from iPhoto 09 to a file, to burn a CD, after 35 photos it stops copying and I get "Unable to create/users/dividrublesr/ documents/I don't know what is going on.

    When copying pic from iPhoto 09 to a file, to burn a CD, after 35 photos it stops copying and I get "Unable to create/users/dividrublesr/ documents/I don't know what is going on. Forgive me for any mistakes, I am a first timer.

    Given that the file is selected then the next possibility is that you're exporting two files with the same name. When you do this the export breaks down as the second file would overwrite the first. Check the filenames.
    Regards
    TD

  • Unable to create follow-up document in Portal

    Hi,
    We are using NetWeaver Portal 7.0 and it is at the latest SP(SP10).
    When we are trying to create a follow-up document for an opportunity all the fields are getting grayed out and we are unable to create any follow-up document.But from GUI we are able to create it successfully.
    Also we are unable to create any sub-opportunity for the existing opportunity
    Both the above were possible when the portal was on lower SP(SP8)
    Does this issue have anything to do with the SP upgrade or could there be any other reason.
    Any inputs on the above issue would be of great help.
    Thanks and Regards,
    Vijaya Sai.

    Hi Chen,
    The problem the you are facing mostly occurs due to incorrect assignment of roles. The user id that is used in the EP needs to be present in the CRM backend system as well. The CRM Backend user has to be assigned to the corresponding single role.
    Portal user needs to be assigned to a Portal Role.
    Kindly have a look at the following document which will give more
    information on the role configuration.
    Please find the related documentation under:
    -> http://service.sap.com/crm-inst
    -> People-Centric CRM Inst. a. Config. Guides (on the left side tree)
    Kindly have a look at the guide for CRM 5.0
    This will give a clear picture on how to set up follow ups. Hope this helps. Please let us know incase you need more information on the same.
    Regards,
    Hemanth

  • After creating a sales document type in tvak

    after creating a new sales document type in tvak what next to link it to BP number.

    Hi
    it should be done via configuration, not using the tcode
    goto SPRO
    press F5
    search for SALES DOCUMENT TYPES
    <b>in sales & distribution
    sales
    sales documents
    sales document header
    define sales document types</b>
    there you have to add extra new entries
    Regards
    Anji

  • Unable to create the sales team record using api AS_ACCESS_PUB.create sales

    Hi all,
    Please help with any sample code to create the sales team using AS_ACCESS_PUB.create sales team.
    When i am initialising,i am getting AS_SALES_MEMBER_PVT USing Fn error
    If i am not initialising,i am getting cannot read the value for profile option user_id;
    Regards,
    Raj

    Hi Ankitha,
    Your scenario is very vague.
    You have got the PO in the client 130 system and you wanted to created a SO in the same client 130 system.
    Usually we don't create a SO using the PO from the same system. Instead of using an IDOC concept, Call the BAPI BAPI_SALESORDER_CREATEFROMDAT1 or BAPI_SALESORDER_CREATEFROMDAT2.
    You can use any of the 2 BAPI's to create the sales order.
    Write a custom program to call the BAPI and assign that custom program as a driver program to your output type which is being triggered in the PO document, then as soon as that output type is triggered it creates the sales order for you.
    My sincere suggestion just counter check your requirement with the concerned persons as we don't generally create a sales order by referencing the po in the same system, but we create a po by referencing a so in the same system for Third party sales orders.
    Thanks,
    Mahesh.

  • Unable to create a billing document , have to change the posting date

    Dear All,
                      I have performed the following steps:
                     1. I have created Customer
                     2. Created a material.
                     3. Linked the customer to the material
                     4. Post initial stock for the material.
                     5. Create a Sales/Order.
                     6. Displayed the sales order and recorded the scheduled delivery date.
                     7. Created the delivery for the sales order.
                     8. Transfer the stock from the warehouse management
                     9. And update the order.
    While updating the order I selected post goods issue and it would not go ahead because the posting date is not there in the posting period. Where do I change the posting date. I could not find it anywhere. I did not enter the date anywhere.
    Thank you,
    Sandhya

    Hello Sandhya
    Here is how MMPV works.
    Lets say I am at the end of the May month 05.31.2009 so lets say period corrresponding to this is 05/2009.
    Now if you want to post data in June perios 06/2009 should be opened.
    Here is what I will do in MMPV
    Enter my company code
    Instead of using periods I will use date which will be 06/01/2009 (mm/dd/yy format in my example)
    Check radio button check and close period
    Click on remaining checkboxes.
    Execute
    The effect of this will be that the previous periods will be closed and June will be opened.
    In your case since no one has opened periods after 2006 so may be you will have to repeat this step for each month until you reach current period if that is the one in which you want to post goods issue.
    Thanks
    Vikas

  • Unable to Create/Update Sales Party Object via FA Web Service Calls.

    Invoking the updateSalesParty() and createSalesParty() methods of the Web Service proxy doesn't show any errors, but at the same time, it doesn't create or update the Sales party objects on the Fusion instance.
    ( https://rws-fap0267-crm.oracledemos.com/crmCommonSalesParties/SalesPartyService?WSDL )
    I've attached the java code and console output when I run the code for your ready reference.
    Any pointers on what I'm missing will be very helpful.
    Thanks in advance!
    Cheers,
    Sharath

    I tried invoking the WS -via SOAPUI - using the payload specified in WebService Sample Payload for Creating a Sales Account (Doc ID 1362190.1) and I get the follow error response.
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
      <env:Header/>
      <env:Body>
          <env:Fault>
            <faultcode>env:Server</faultcode>
            <faultstring><![CDATA[JBO-27023: Failed to validate all rows in a transaction.JBO-27024: Failed to validate a row with key oracle.jbo.Key[300000077245710 ] in OrganizationDEOJBO-27014: Attribute Type_c in OrganizationDEO is required.JBO-27014: Attribute Type_c in OrganizationDEO is required.JBO-27024: Failed to validate a row with key oracle.jbo.Key[300000077245711 ] in PartySiteEOJBO-HZ:::HZ_NO_LOCATION_FOUND: <MESSAGE><NUMBER>HZ-120085</NUMBER><TEXT>The location 958 is invalid. Use a valid location from the HZ_LOCATIONS table.</TEXT><CAUSE></CAUSE><ACTION></ACTION><DETAILS></DETAILS><INCIDENT></INCIDENT></MESSAGE>JBO-27024: Failed to validate a row with key oracle.jbo.Key[300000077245712 ] in PartySiteUseEO: nullJBO-27024: Failed to validate a row with key oracle.jbo.Key[300000077245714 ] in PartyUsageAssignmentEO: null]]></faultstring>
            <detail>
                <tns:ServiceErrorMessage xmlns:tns="http://xmlns.oracle.com/adf/svc/errors/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                  <tns:code>27023</tns:code>
                  <tns:message>JBO-27023: Failed to validate all rows in a transaction.</tns:message>
                  <tns:severity>SEVERITY_ERROR</tns:severity>
                  <tns:detail xsi:type="tns:ServiceRowValErrorMessage">
                      <tns:code>27024</tns:code>
                      <tns:message>JBO-27024: Failed to validate a row with key oracle.jbo.Key[300000077245710 ] in OrganizationDEO</tns:message>
                      <tns:severity>SEVERITY_ERROR</tns:severity>
                      <tns:detail xsi:type="tns:ServiceAttrValErrorMessage">
                        <tns:code>27014</tns:code>
                        <tns:message>JBO-27014: Attribute Type_c in OrganizationDEO is required.</tns:message>
                        <tns:severity>SEVERITY_ERROR</tns:severity>
                        <tns:exceptionClassName>oracle.jbo.AttrValException</tns:exceptionClassName>
                        <tns:attributeName>Type_c</tns:attributeName>
                        <tns:objectName>OrganizationDEO</tns:objectName>
                      </tns:detail>
                      <tns:detail xsi:type="tns:ServiceAttrValErrorMessage">
                        <tns:code>27014</tns:code>
                        <tns:message>JBO-27014: Attribute Type_c in OrganizationDEO is required.</tns:message>
                        <tns:severity>SEVERITY_ERROR</tns:severity>
                        <tns:exceptionClassName>oracle.jbo.AttrValException</tns:exceptionClassName>
                        <tns:attributeName>Type_c</tns:attributeName>
                        <tns:objectName>OrganizationDEO</tns:objectName>
                      </tns:detail>
                      <tns:exceptionClassName>oracle.jbo.RowValException</tns:exceptionClassName>
                      <tns:objectName>OrganizationDEO</tns:objectName>
                  </tns:detail>
                  <tns:detail xsi:type="tns:ServiceRowValErrorMessage">
                      <tns:code>27024</tns:code>
                      <tns:message>JBO-27024: Failed to validate a row with key oracle.jbo.Key[300000077245711 ] in PartySiteEO</tns:message>
                      <tns:severity>SEVERITY_ERROR</tns:severity>
                      <tns:detail xsi:type="tns:ServiceRowValErrorMessage">
                        <tns:code>HZ:::HZ_NO_LOCATION_FOUND</tns:code>
                        <tns:message><![CDATA[JBO-HZ:::HZ_NO_LOCATION_FOUND: <MESSAGE><NUMBER>HZ-120085</NUMBER><TEXT>The location 958 is invalid. Use a valid location from the HZ_LOCATIONS table.</TEXT><CAUSE></CAUSE><ACTION></ACTION><DETAILS></DETAILS><INCIDENT></INCIDENT></MESSAGE>]]></tns:message>
                        <tns:severity>SEVERITY_RECOVERABLE_ERROR</tns:severity>
                        <tns:exceptionClassName>oracle.jbo.RowValException</tns:exceptionClassName>
                        <tns:objectName>PartySiteEO</tns:objectName>
                      </tns:detail>
                      <tns:exceptionClassName>oracle.jbo.RowValException</tns:exceptionClassName>
                      <tns:objectName>PartySiteEO</tns:objectName>
                  </tns:detail>
                  <tns:detail xsi:type="tns:ServiceRowValErrorMessage">
                      <tns:code>27024</tns:code>
                      <tns:message>JBO-27024: Failed to validate a row with key oracle.jbo.Key[300000077245712 ] in PartySiteUseEO</tns:message>
                      <tns:severity>SEVERITY_ERROR</tns:severity>
                      <tns:detail xsi:type="tns:ServiceErrorMessage">
                        <tns:severity>SEVERITY_ERROR</tns:severity>
                        <tns:exceptionClassName>java.lang.NullPointerException</tns:exceptionClassName>
                      </tns:detail>
                      <tns:exceptionClassName>oracle.jbo.RowValException</tns:exceptionClassName>
                      <tns:objectName>PartySiteUseEO</tns:objectName>
                  </tns:detail>
                  <tns:detail xsi:type="tns:ServiceRowValErrorMessage">
                      <tns:code>27024</tns:code>
                      <tns:message>JBO-27024: Failed to validate a row with key oracle.jbo.Key[300000077245714 ] in PartyUsageAssignmentEO</tns:message>
                      <tns:severity>SEVERITY_ERROR</tns:severity>
                      <tns:detail xsi:type="tns:ServiceErrorMessage">
                        <tns:severity>SEVERITY_ERROR</tns:severity>
                        <tns:exceptionClassName>java.lang.NullPointerException</tns:exceptionClassName>
                      </tns:detail>
                      <tns:exceptionClassName>oracle.jbo.RowValException</tns:exceptionClassName>
                      <tns:objectName>PartyUsageAssignmentEO</tns:objectName>
                  </tns:detail>
                  <tns:exceptionClassName>oracle.jbo.TxnValException</tns:exceptionClassName>
                </tns:ServiceErrorMessage>
            </detail>
          </env:Fault>
      </env:Body>
    </env:Envelope>
    Is there a way to see this error response when invoking the WS via a Java client-proxy?

  • How to create a sales document using  BAPI_SALESORDER_CREATEFROMDAT2

    Hai i was un able to create a sales order using the BAPI can you help me out

    Sample Code:
              clear:   l_order_header,
                       l_salesdocument,
                       l_order_partners,
                       l_order_items,
                       l_order_schdl.
              refresh: it_order_items,
                       it_order_partners,
                       it_order_schdl,
                       it_return.
    ???????? get from material ...
            Order header
              l_order_header-doc_type          = 'ZQBV'.
              l_order_header-distr_chan        = '10'.
              l_order_header-division          = '00'.
              if g_qals-werk eq '1100'.
                l_order_header-sales_org         = '1000'.
              else.
                if g_qals-werk eq '3100'.
                  l_order_header-sales_org         = '3000'.
                else.
                  message i001(00) with text-005.
                endif.
              endif.
              l_order_header-purch_no_c        = g_qals-prueflos.  " <= lot
            Partner data
              l_order_partners-partn_role      = 'AG'.
              l_order_partners-partn_numb      = g_qals-kunnr.
              append l_order_partners to it_order_partners.
            Order items => only one
              l_order_items-itm_number         = 10.
              l_order_items-material           = g_qals-matnr.
              l_order_items-target_qty         = 1.
              append l_order_items to it_order_items.
            Schedules for quantity
              l_order_schdl-itm_number         = 10.
              l_order_schdl-req_qty            = 1.        " <=  only 1 !
              append l_order_schdl to it_order_schdl.
            Conditions for value
              l_order_conditions-itm_number    = 10.
              l_order_conditions-cond_type     = 'PR00'.
              l_order_conditions-cond_value    = g_effort_sum.
              l_order_conditions-currency      = g_effort_unit.
              append l_order_conditions to it_order_conditions.
            BAPI to create sales order
              CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
                EXPORTING
               SALESDOCUMENTIN               =
                  ORDER_HEADER_IN               = l_order_header
               ORDER_HEADER_INX              =
               SENDER                        =
               BINARY_RELATIONSHIPTYPE       =
               INT_NUMBER_ASSIGNMENT         =
               BEHAVE_WHEN_ERROR             =
               LOGIC_SWITCH                  =
               TESTRUN                       =
               CONVERT                       = ' '
                IMPORTING
                  SALESDOCUMENT                 = l_salesdocument
                TABLES
                  RETURN                        = it_return
                  ORDER_ITEMS_IN                = it_order_items
               ORDER_ITEMS_INX               =
                  ORDER_PARTNERS                = it_order_partners
                  ORDER_SCHEDULES_IN            = it_order_schdl
               ORDER_SCHEDULES_INX           =
                  ORDER_CONDITIONS_IN           = it_order_conditions
               ORDER_CONDITIONS_INX          =
               ORDER_CFGS_REF                =
               ORDER_CFGS_INST               =
               ORDER_CFGS_PART_OF            =
               ORDER_CFGS_VALUE              =
               ORDER_CFGS_BLOB               =
               ORDER_CFGS_VK                 =
               ORDER_CFGS_REFINST            =
               ORDER_CCARD                   =
               ORDER_TEXT                    =
               ORDER_KEYS                    =
               EXTENSIONIN                   =
               PARTNERADDRESSES              =
              if not l_salesdocument is initial.
              order successfully created
                message i001(00) with text-001 l_salesdocument.
    call function 'BAPI_TRANSACTION_COMMIT'.
              endif.
    Regards,
    Ravi

  • Unable to create follow on documents in SOCO

    Hi all,
    We are on SRM Server 550 SPS: SAPKIBKT05
    Once I click 'propose source of supply', it takes me to the next screen showing the proposed SOS's in a subscreen.
    Below this, is another subsreen with three tabs. Currently I do not see anything here? No items.
    Any idea what problem could it be? Do I need to activate BW report templates? Or is there something else??
    Thanks.
    Ali

    Hi,
    BW reports don't cause it. They will be used for reporting vendor evaluation etc.
    There are few things to make SOS to work:
    - material and services must exists in COMMPR01
    - in COMMPR01 Conditions tab must be filled with proper values eg.
      - Ctyp = 01PV
      - Vendor = 332 (Business Partner number)
      - Ammount = 34,00
      - Currency = EUR
      - Valid from = 25.10.2006
      - Valid to = 31.12.9999
    - in COMMPR01 Relationships->Vendor tab:
      - Business Partner = 332
    Save document.
    These values will be show in SOS. In Overview of Sources of Supply will be vendor no 332.
    Please check if Your IPC is work correctly in SPRO->SRM->SRM Server->Cross-Application Basic Settings->Pricing->Check Technical and Customizing Settings for Conditions
    Please look at SAP note 881265, 778253 too.
    Regards,
    Marcin

  • Unable to block creation of sales document from Quotation thru user status

    Dear Experts,
    I have maintained a status profile in my Quotation document through the use of user status. I have defined a status to forbid creation of sales document if the status has not yet been set to "Approved".
    However, even when the status is not yet "Approved", it still allows me to create subsequent sales document from this Quotation.
    Anything that I have missed here?

    Hi,
    It should not happen.
    Please check the Object types for which the status profile is created. It should be for either Sales Order header or Sales order Item.
    Make sure that the "create sales document" is "forbiddden" for the initial status only.
    Also please check Low- High numbers for each status.
    Hope this helps.
    Regards,
    Sharan

  • Sales document created from CRM 4.0 needs to be updated from ECC 6.0

    Hello experts,
    When I create one sales document from CRM 4.0 this document is moved to ECC 6.0. But updating sales document from ECC 6.0 I receive message
                 "Process the original document in the CRM system"
    and updates are not moved to CRM.
    How could I avoid this ?
    Usually I need update some fields from ECC 6.0 and move the information to CRM.
    Regards
    Juan

    Hi Juan,
    Please check the Note 541113 - Data exchange scenarios for orders (CRM-R/3) in which as per your requirement its the scenario Z i.e you want some data to flow from ECC to CRM for which below are the settings that needs to be done to make it effective.
    Activation of the scenario in table CRMPAROLTP of the R/3 plug-in:
    PARNAME:   CRM_SCENARIO
    PARNAME2:  UPLOAD_ORDER
    PARVAL1:   Z
    Go to SM30 and give the table name and put in the above values.
    And if you want to make amutual change situation then proceed as follows:
    Settings in the CRM Server: Table SMOFPARSFA
               Key: R3A_SALES
               Parameter Name 1: INT_CHANGE_ORDER
               Parameter Name 2: <sales document type> , for example TA
               Parameter Value 1: Z
    Settings in the R/3 system: table CRMPAROLTP
               Parameter Name: CRM_SCENARIO
               Parameter Name 2: INT_CHANGE_ORDER
               Parameter Name 3: <sales document type> , for example TA
               Parameter Value: Z
    Hope it helps.
    Regards
    Sidd

Maybe you are looking for