Error during  Performing Setup - SD Sales Orders...

Hi gurus,
I am getting an error while Performing Setup - SD Sales Orders by following the below steps from SAP best practices document for Sales Overview cube(0SD-C03).
In the Display IMG view choose Data Transfer to the SAP Business Information Warehouse à Settings for Application-Specific DataSources à Logistics à Managing Extract Structures à Initialization à Filling in the Setup Table  Application-Specific Setup of Statistical Data  SD-Sales Orders - Perform Setup.
ERROR MESSAGE IS: "Error determining rate: foreign curr. local curr.
USD date 11/06/2005(doc. 9153)"
Thanks.
Syed.
Note: This topic is marked as questions and will be rewarded with points.

hi Syed,
you can use transaction SNOTE,
and menu go to->sap note browser, find if that oss note is there. this note quite old (2001).
manually, you can check program LSCUNF01 (SE38),
and compare with following (for r/3 4.6a - 4.6d),
depend on your r/3 version.
please ask basis help.
FORM ABWCT_EXIST
Delta 001
Context Block
FORM abwct_exist USING loc_curr for_curr exc_date
                                         value(exc_type).
*------- DATC enthält das invertierte Datum -
  CONVERT DATE exc_date INTO INVERTED-DATE datc.
Delete Block
Insert Block
*----- TCURV als erstes lesen, falls Invertierung aktiv -
  IF tcurv-kurst NE exc_type OR tcurv-mandt NE mandt.
    SELECT SINGLE * FROM  tcurv CLIENT SPECIFIED
           WHERE  kurst       = exc_type
            AND   mandt       = mandt.
  ENDIF.
Delta 002
Context Block
      ENDIF.
    ENDIF.
Alter Eintrag nicht verwendbar -
  ELSE.
Delete Block
*----- TCURV als erstes lesen, falls Invertierung aktiv -
    IF tcurv-kurst NE exc_type OR tcurv-mandt NE mandt.
      SELECT SINGLE * FROM  tcurv CLIENT SPECIFIED
             WHERE  kurst       = exc_type
              AND   mandt       = mandt.
    ENDIF.
Insert Block

Similar Messages

  • Error during batch determination in sales order

    Hi all,
    I have this information error during batch determination: LB059 " Error when mixing configuration and selection criteria" .
    Does anyone know what i´m doing wrong?
    We are using materials with characteristics, and when i try the batch determination in a sales order, i got this messagge.
    Thank you all!!

    Hello Juan
    The characteristics you used to configure the product in the sales order are passed dynamically during run time as selection criteria to determine a matching class and that's where the problem is happening.
    Sit with an ABAPer to debug and find out what's the issue. Your focus for this activity should be on the following includes to Program SAPLV01F:
    LV01FFC1
    and
    LV01FM01
    More specifically, test the following Function Modules with your live data to figure out which one is failing:
    CLO0_DDB_OBJ_VALUATION_OPEN
    CTMS_DDB_HAS_CHARACTERISTICS
    CTMS_DDB_HAS_VALUES
    CTMS_DDB_DEL_VALUE
    CTMS_DDB_SET_VALUE_INTERNAL
    CLO0_DDB_OBJ_VALUATION_CLOSE
    Hope this helps. Sorry it is hard to give a functional type of response to this very technical issue.

  • Internal error during pricing in CRM sales order

    Hi,
      While creating sales order i am getting following error in sales order
      Internal error during pricing.
      i am not understading what will be the cause of error
      currently working on CRM 7.0
    we have replicated all pricing condition types from ECC
    Thanks & Regards
    kishore kumar

    Hello kishore kumar,
    Tell basis Team to restart Java Instances.
    After that check in Sales Order. If you still get that error then download below objects in a Sequence.
    1. DNL_CUST_CNDALL
    2. DNL_CUST_CND
    3.DNL_CUST_PRC
    Regards,
    Rajendra

  • Error during PGR in return sales order

    HI all,
    I m encountering an error as shown in pic during Post goods receipt of returns delivery by vl02n.
    message details
    Message Text
    Error in creating post goods issue
    Technical Data
    Message type__________
    E (Error)
    Message class_________
    M7 (Inventory Management and Physical Inventory)
    Message number________
    593
    Message variable 1____
    Message variable 2____
    Message variable 3____
    Message variable 4____
    Message Attributes
    Level of detail_______
    Problem class_________
    Sort criterion________
    Number________________
                                                                                                                                        1
    Environment Information
    Item__________________
    000010
    Material______________
    000000000000xxxx
    Description___________
    bhjbhbj
    Sales unit____________
    KG
    Batch_________________
    1234
    Message Number________
    593
    Message Type__________
    E
    Application Area______
    M7
    Message variable______
    Message variable______
    how can i solve this??? Is it related to movement type 651 or something else?

    First check what movement type is assigned for this return sales process.  Next try to execute via VL10A or VL10C and post here your update.  Also I am not sure, why system is showing
    Error in creating post goods issue
    for returns?  Ideally, it should have been post goods receipt.  Check in Service Marketplace whether any note is there for this error message number.
    G. Lakshmipathi

  • Account Assignment Error When Posting GI Against Sales Order

    Hello SAP Experts,
    We are currently experiencing a problem during goods issueance against sales order (VL02N). The system terminates the issueance and gives error:
    "Account XXXXXX requires an assignment to a CO object".
    We have tried maintaining the GL account in OKB9 and assign a default profit center there but i didn't work. The material master also contains the profit center. We were only able to post the transaction if we try to default the a cost center in FS00. However we dont want to assign a default cost center as cost centers differ by plant. We are wondering why it asks the cost center considering that it already contains the sales order assignment. We checked the field selection of the GL account, movement type and even the posting key and all showed that the cost center is not required. We are now in a dead end situation here. Please please help us.
    Thanks in advance!

    Hello Praveen,
    Thank you for your immediate response.
    What confuses me is the fact that it asks for a CO element when in fact it is already assigned to one (it is goods issuance against sales order). Do you know why is the system behaving that way?
    Thanks!.

  • Standalone Scenario - Error during Creation of Local Purchase Order

    Hi All,
         I am trying to setup Standalone Scenario, i have created all the master data locally, i am able to Order SC, but after workflow approval SC goes into error 'Error during creation of local purchase order from shopping cart XXXXXXXXX'
         I have created following configuration setting for local PO number
    1) In SPRO -> Cross-Application Basic Settings -> Number Ranges -> Define Number rang. for Schopping Carts and Follow-on Doc. --- i have number ranges for PO follow-on doc. i.e.
    inrerval No = PO, from number = 0004000000, to number = 0004999999, ext. = unchecked
    2) In SPRO -> Cross-Application Basic Settings -> Number Ranges -> Define Ranges per backend system for follow-on documents PO, PR etc
    3) In sourcing (SPRO -> Cross-Application Basic Settings -> Sourcing -> Define Interactive Sourcing for product categories) ---  sourcing is never carried out.
    Can anybody help?
    Regards,
    SAP Guy.
    Edited by: SAP Guy on Apr 23, 2008 2:32 AM

    Hi SAP Guy,
    Following steps are must for Local number range
    1) Create number range for local PO
    2) Maintain your logical system in 'Define number range per backend system for follow on document'
    3) Define Transaction Type for BUS2201, define document type (e.g. EC1)
    4) Assign Document type (EC1) in Org attribute BSA.
    Hope this helps.
    Regards,
    Manish.

  • Error during material determination for sales document item - RRB

    Hi
    Iam getting following error when trying to create a billing request using DP91.
    Error during material determination for sales document item 40001560/000010
    Message no. AD01155
    Diagnosis
    An error occured during material determination for a dynamic item.
    System Response
    The system cannot perform the function.
    Procedure
    Check in the profile being used whether its characteristic allows the assignment of a material to each dynamic item.
    I have checked my DIP profile using ODP02 there are no errors in it, I have created a Setid and assigned it to costing element in selection criteria and material determination criteria.
    Material origin is checked in costing tab in material master.
    Appreciate help in resolving this.
    thanks,
    Vaishnavi

    Hi Vaishnavi
    The error which you are getting is related to costing.So kindly reach your FI Consultant
    please check the following links which may help you.Also check the link that has been provided my Lakshmipathi
    ERROR AT DP90  TRANSACTION
    Regards
    Srinath

  • In DP50 Error during material determination for service order

    Hi,
    While doing Resources-Related Billing request,the following error is displaying..
    Kindly Help
    Error during material determination for service order
    Message no. AD01156
    Diagnosis
    An error occured during material determination for a dynamic item.
    System Response
    The system cannot perform the function.
    Procedure
    Check in the profile being used whether its characteristic allows the assignment of a material to each dynamic item.
    501384
    Message no. AD01156
    Diagnosis
    An error occured during material determination for a dynamic item.
    System Response
    The system cannot perform the function.
    Procedure
    Check in the profile being used whether its characteristic allows the assignment of a material to each dynamic item.
    Thanks,
    Mohit

    Hi mohit,
    You need to check DIP profile setting if profile is attached to your order type or not please check this
    Thanks and regards
    Sachin Kadam

  • SDK Error -5002 when adding a sales order

    I'm getting an error -5002 when adding a sales order.
    Source code:
          IDocuments m_so2 = SBOCOMUtil.newDocuments(icmp, SBOCOMConstants.BoObjectTypes_Document_oOrders);
          line = m_so2.getLines();
          m_so2.setCardCode("2173231916");
          m_so2.setCardName("test Sales order");
          SimpleDateFormat formatter = new SimpleDateFormat("dd.MM.yyyy");
          Date today = Calendar.getInstance().getTime();
          m_so2.setDocDueDate(today);
          line.setItemCode("01005");
          line.setDiscountPercent(new Double(10));
          line.setItemDescription("description Testing");
          line.setQuantity(new Double(3));
          line.setTaxCode("0");
          line.add();
          long rc = m_so2.add();
    Question:
    Where can I find a list of error codes that can be easy to understand? PDF, word, etc.
    Thanks.

    Hi Diego,
    Looking at your code I see that you are doing a
    line.add();
    You don’t need to have this here unless you are adding another line to your document.
    Maybe this will help you.
    Also just because java is a bit different from VB get the last error message using
    SBOErrorMessage errMsg= comp.getLastError();
    System.out.println(errMsg.getErrorMessage());
    -Cormac

  • Hi Sanjeev : Validating PO during the creation of Sales Orders

    Hi Sanjeev,
    Thank you very much for helping me out in this problem.Still I haven't got the solution.
    I tested the above mentioned configuration option by putting the Check Purchase Order Number field to 'A' in the transaction VOV8. But while creating sales orders, it is giving only information message. Is there any other way, to restrict the Duplicate PO value through configuration setup.
    can you also explain how to use Enqueue and Dequeue FMs in the inbound posting function module.
    Regards,
    Madhusudan.

    Hi
    This is in customizing transaction SPRO -> SALES & DIST -> SALES -> SALES DOCUMENTS -> DEFINE VARIABLE MESSAGES.
    I am pasting the help from customizing note
    Define Variable Messages
    Various checks are carried out during scheduling agreement processing with releases in the component supplier industry. Depending on the result of the check, the system can issue a warning or an error message. In this menu option, you can define which system response is to be linked to a particular message text.
    Depending on the component supplier, you can specify whether certain system messages are to be sent as errors, as warning messages or not at all. By specifying a version, system responses can be specified by component supplier.
    Example
    When a forecast delivery schedule is created, the system compares the cumulative received quantities of the customer with the cumulative received quantities in the document flow at the time at which the delivery note was created. You can configure the system to issue an error message if these do not correspond.
    Standard system
    Two system responses can be configured in the standard system:
    The message appears as a warning.
    The message appears as an error.
    In the standard system the messages are configured to appear as warnings.
    Actions
    1. Enter a message class and the message text and specify the system response.
    2. If you want to use different versions for certain component suppliers, you copy a message and enter a version number together with the required system response.

  • Product allocation not working even after complete setup at sales order lvl

    Hi All,
    I have setup product allocation as detailed in forum earlier links, still I am not gettin sales order to use ATP with product allocation. I have tried with S140 and S700 with no success. Already went thru all the steps starting with OVZ* tcode. And during allocation check I can see the part number which has PRODUCT ALLOC procedure assigned. So, what is missing?
    Appreciate if someone can provide me with a SAP documentation to make sure I can recheck the settings one final time.
    Thanks.
    Naren

    It worked but doesn't seem to suit business requirement.

  • Run Time Error while Entering Quantity in Sales Order

    Dear All,
    Iam getting Run time Error while iam entering material quantity in sales order.Please  find the screenshot of the same.
    kindly Help Me.Me. Plz note that we had done a system copy two days back to our new server.
    Rgds
    Thomson
    ST22 Screenshot

    Dear All
    Its Resolved Thanks For your Valuable time Support
    INCLUDE LV03VFB4 inside below code trigger error.
    PERFORM VVBBD_AUFBAUEN USING WA_AVBBD
                                        WA_AVBBD-APOMOBILE
                                        DA_SUBRC
                                        DA_UPDKZ
                                        DA_VVBBD_TABIX
                                        0.
    This Was the Error some how 0 was there we are removed the 0 now it is working fine
    Rgds
    Thomson

  • Error during scheduling while running Run order sequencing in PPR

    Hello Experts,
    An error saying 'Error during scheduling' is logged while running Run order sequencing in Production Planning Run and the job is failed.
    Checked the capacity of the resource but seems ok.
    The below long text is displayed next to the error message.
    Error during scheduling
    Message no. /SAPAPO/OM043
    Diagnosis
    The system could not schedule an order, operation or activity.
    This could have the following causes:
    The resource does not have any free working time or capacity.
    If you have set planning direction backwards in the strategy profile:
    There is not enough working time or capacity available for scheduling between now and the scheduling date.
    If you have set planning direction forwards in the strategy profile:
    There is not enough working time or capacity available for scheduling between the scheduling date and the end of the planning area.
    If you plan characteristics-dependently:
    You have assigned characteristics to operations of the order that do not agree with characteristics of the resources on which the operations are to be processed.
    The system cannot find any suitable characteristics on the resources and so it cannot schedule.
    Procedure
    Depending on which of the above reasons is the cause, change the following settings:
    Change the working times and capacities of the resources.
    Set the planning mode "infinite planning" in the strategy profile.
    Activate the planning direction forwards or backwards and reverse in the strategy profile.
    Change the characteristics that you have assigned to the resource.
    Can anyone let me know what else need to check to avoid the error.

    Dear Maddy,
    The function "Reschedule" follows an all-or-nothing logic, which means that either all selected activities on a resource can be re-scheduled or the function (better the liveCache) cancels and no activities will be re-scheduled.
    One reason might be that you have a pegging relation to a fixed activity (this might be a sales order, forecast, an activity outside the propagation range...) which cannot be considered during the
    scheduling. The liveCache cannot break the pegging, therefore it cancels the scheduling.
    Please have a look at the note 510669 which offers a heuristic on the basis of the algorithm /SAPAPO/HEUR_PLAN_SEQ_PACKAGES. This heuristic should solve your problem. It will re-schedule as many activities as possible and will not cancel if one fails.
    Depending on your current release there could be also some correction notes like
    1272960
    1027194
    I hope I could help you further.
    Regards,
    Tibor

  • Error while trying to create sales order using oe_order_pub.process_order

    Hi All,
    I am trying to create a sales order using oe_order_pub.process_order api..
    The Procedure i had written is as follows.
    CREATE OR REPLACE PROCEDURE TEST_PROC
    AS
    x_return_status VARCHAR2(250);
    x_msg_count NUMBER;
    x_msg_data VARCHAR2(250);
    F varchar2(2000);
    --out parameters
    x_header_rec OE_Order_PUB.Header_Rec_Type;
    x_header_val_rec OE_Order_PUB.Header_Val_Rec_Type;
    x_Header_Adj_tbl OE_Order_PUB.Header_Adj_Tbl_Type;
    x_Header_Adj_val_tbl OE_Order_PUB.Header_Adj_Val_Tbl_Type;
    x_Header_price_Att_tbl OE_Order_PUB.Header_Price_Att_Tbl_Type;
    x_Header_Adj_Att_tbl OE_Order_PUB.Header_Adj_Att_Tbl_Type;
    x_Header_Adj_Assoc_tbl OE_Order_PUB.Header_Adj_Assoc_Tbl_Type;
    x_Header_Scredit_tbl OE_Order_PUB.Header_Scredit_Tbl_Type;
    x_Header_Scredit_val_tbl OE_Order_PUB.Header_Scredit_Val_Tbl_Type;
    x_line_tbl OE_Order_PUB.Line_Tbl_Type;
    x_line_val_tbl OE_Order_PUB.Line_Val_Tbl_Type;
    x_Line_Adj_tbl OE_Order_PUB.Line_Adj_Tbl_Type;
    x_Line_Adj_val_tbl OE_Order_PUB.Line_Adj_Val_Tbl_Type;
    x_Line_price_Att_tbl OE_Order_PUB.Line_Price_Att_Tbl_Type;
    x_Line_Adj_Att_tbl OE_Order_PUB.Line_Adj_Att_Tbl_Type;
    x_Line_Adj_Assoc_tbl OE_Order_PUB.Line_Adj_Assoc_Tbl_Type;
    x_Line_Scredit_tbl OE_Order_PUB.Line_Scredit_Tbl_Type;
    x_Line_Scredit_val_tbl OE_Order_PUB.Line_Scredit_Val_Tbl_Type;
    x_Lot_Serial_tbl OE_Order_PUB.Lot_Serial_Tbl_Type;
    x_Lot_Serial_val_tbl OE_Order_PUB.Lot_Serial_Val_Tbl_Type;
    x_action_request_tbl OE_Order_PUB.Request_Tbl_Type;
    --in parameters
    l_header_rec OE_Order_PUB.Header_Rec_Type;
    t_line_tbl OE_ORDER_PUB.Line_Tbl_Type;
    BEGIN
    apps.mo_global.set_org_context(204,null,'ONT');
    l_header_rec := OE_ORDER_PUB.G_MISS_HEADER_REC;
    l_header_rec.ORG_ID := 204;
    l_header_rec.ORDER_TYPE_ID := 1437;
    l_header_rec.SOLD_TO_ORG_ID := 1290;
    l_header_rec.SHIP_TO_ORG_ID:=1425;
    l_header_rec.INVOICE_TO_ORG_ID:=1424;
    l_header_rec.PRICE_LIST_ID := 1000;
    l_header_rec.salesrep_id := 1006;
    l_header_rec.ORDER_CATEGORY_CODE := 'MIXED';
    l_header_rec.VERSION_NUMBER := 0;
    l_header_rec.OPEN_FLAG := 'Y';
    l_header_rec.BOOKED_FLAG := 'Y';
    l_header_rec.PRICING_DATE := sysdate;
    l_header_rec.TRANSACTIONAL_CURR_CODE := 'USD';
    l_header_rec.created_by := FND_GLOBAL.USER_ID;
    l_header_rec.creation_date := sysdate;
    l_header_rec.LAST_UPDATED_BY := FND_GLOBAL.USER_ID;
    l_header_rec.LAST_UPDATE_DATE := sysdate;
    l_header_rec.attribute1 := '250';
    l_header_rec.operation := 'CREATE';
    t_line_tbl(1) := OE_ORDER_PUB.G_MISS_LINE_REC; ---check
    t_line_tbl(1).inventory_item_id := 193742;
    t_line_tbl(1).ordered_quantity := 1;
    t_line_tbl(1).operation := 'CREATE';
    oe_debug_pub.initialize;
    --oe_debug_pub.SetDebugLevel(1);
    OE_MSG_PUB.INITIALIZE();
    OE_Order_PUB.Process_Order
    ( -- p_org_id => 204,
    --p_operating_unit => 'ONT',
    p_api_version_number => 1.0,
    p_init_msg_list => FND_API.G_TRUE,
    p_return_values => FND_API.G_TRUE,
    p_action_commit => FND_API.G_TRUE,
    x_return_status => x_return_status,
    x_msg_count => x_msg_count,
    x_msg_data => x_msg_data,
    p_header_rec => l_header_rec,
    p_old_header_rec => OE_Order_PUB.G_MISS_HEADER_REC,
    p_header_val_rec => OE_Order_PUB.G_MISS_HEADER_VAL_REC,
    p_old_header_val_rec => OE_Order_PUB.G_MISS_HEADER_VAL_REC,
    p_Header_Adj_tbl => OE_Order_PUB.G_MISS_HEADER_ADJ_TBL,
    p_old_Header_Adj_tbl => OE_Order_PUB.G_MISS_HEADER_ADJ_TBL,
    p_Header_Adj_val_tbl => OE_Order_PUB.G_MISS_HEADER_ADJ_VAL_TBL,
    p_old_Header_Adj_val_tbl => OE_Order_PUB.G_MISS_HEADER_ADJ_VAL_TBL,
    p_Header_price_Att_tbl => OE_Order_PUB.G_MISS_HEADER_PRICE_ATT_TBL,
    p_old_Header_Price_Att_tbl => OE_Order_PUB.G_MISS_HEADER_PRICE_ATT_TBL,
    p_Header_Adj_Att_tbl => OE_Order_PUB.G_MISS_HEADER_ADJ_ATT_TBL,
    p_old_Header_Adj_Att_tbl => OE_Order_PUB.G_MISS_HEADER_ADJ_ATT_TBL,
    p_Header_Adj_Assoc_tbl => OE_Order_PUB.G_MISS_HEADER_ADJ_ASSOC_TBL,
    p_old_Header_Adj_Assoc_tbl => OE_Order_PUB.G_MISS_HEADER_ADJ_ASSOC_TBL,
    p_Header_Scredit_tbl => OE_Order_PUB.G_MISS_HEADER_SCREDIT_TBL,
    p_old_Header_Scredit_tbl => OE_Order_PUB.G_MISS_HEADER_SCREDIT_TBL,
    p_Header_Scredit_val_tbl => OE_Order_PUB.G_MISS_HEADER_SCREDIT_VAL_TBL,
    p_old_Header_Scredit_val_tbl => OE_Order_PUB.G_MISS_HEADER_SCREDIT_VAL_TBL,
    p_line_tbl => t_line_tbl,
    p_old_line_tbl => OE_Order_PUB.G_MISS_LINE_TBL,
    p_line_val_tbl => OE_Order_PUB.G_MISS_LINE_VAL_TBL,
    p_old_line_val_tbl => OE_Order_PUB.G_MISS_LINE_VAL_TBL,
    p_Line_Adj_tbl => OE_Order_PUB.G_MISS_LINE_ADJ_TBL,
    p_old_Line_Adj_tbl => OE_Order_PUB.G_MISS_LINE_ADJ_TBL,
    p_Line_Adj_val_tbl => OE_Order_PUB.G_MISS_LINE_ADJ_VAL_TBL,
    p_old_Line_Adj_val_tbl => OE_Order_PUB.G_MISS_LINE_ADJ_VAL_TBL,
    p_Line_price_Att_tbl => OE_Order_PUB.G_MISS_LINE_PRICE_ATT_TBL,
    p_old_Line_Price_Att_tbl => OE_Order_PUB.G_MISS_LINE_PRICE_ATT_TBL,
    p_Line_Adj_Att_tbl => OE_Order_PUB.G_MISS_LINE_ADJ_ATT_TBL,
    p_old_Line_Adj_Att_tbl => OE_Order_PUB.G_MISS_LINE_ADJ_ATT_TBL,
    p_Line_Adj_Assoc_tbl => OE_Order_PUB.G_MISS_LINE_ADJ_ASSOC_TBL,
    p_old_Line_Adj_Assoc_tbl => OE_Order_PUB.G_MISS_LINE_ADJ_ASSOC_TBL,
    p_Line_Scredit_tbl => OE_Order_PUB.G_MISS_LINE_SCREDIT_TBL,
    p_old_Line_Scredit_tbl => OE_Order_PUB.G_MISS_LINE_SCREDIT_TBL,
    p_Line_Scredit_val_tbl => OE_Order_PUB.G_MISS_LINE_SCREDIT_VAL_TBL,
    p_old_Line_Scredit_val_tbl => OE_Order_PUB.G_MISS_LINE_SCREDIT_VAL_TBL,
    p_Lot_Serial_tbl => OE_Order_PUB.G_MISS_LOT_SERIAL_TBL,
    p_old_Lot_Serial_tbl => OE_Order_PUB.G_MISS_LOT_SERIAL_TBL,
    p_Lot_Serial_val_tbl => OE_Order_PUB.G_MISS_LOT_SERIAL_VAL_TBL,
    p_old_Lot_Serial_val_tbl => OE_Order_PUB.G_MISS_LOT_SERIAL_VAL_TBL,
    p_action_request_tbl => OE_Order_PUB.G_MISS_REQUEST_TBL,
    x_header_rec => x_header_rec,
    x_header_val_rec => x_header_val_rec,
    x_Header_Adj_tbl => x_Header_Adj_tbl,
    x_Header_Adj_val_tbl => x_Header_Adj_val_tbl,
    x_Header_price_Att_tbl => x_Header_price_Att_tbl,
    x_Header_Adj_Att_tbl => x_Header_Adj_Att_tbl,
    x_Header_Adj_Assoc_tbl => x_Header_Adj_Assoc_tbl,
    x_Header_Scredit_tbl => x_Header_Scredit_tbl,
    x_Header_Scredit_val_tbl => x_Header_Scredit_val_tbl,
    x_line_tbl => x_line_tbl,
    x_line_val_tbl => x_line_val_tbl,
    x_Line_Adj_tbl => x_Line_Adj_tbl,
    x_Line_Adj_val_tbl => x_Line_Adj_val_tbl,
    x_Line_price_Att_tbl => x_Line_price_Att_tbl,
    x_Line_Adj_Att_tbl => x_Line_Adj_Att_tbl,
    x_Line_Adj_Assoc_tbl => x_Line_Adj_Assoc_tbl,
    x_Line_Scredit_tbl => x_Line_Scredit_tbl,
    x_Line_Scredit_val_tbl => x_Line_Scredit_val_tbl,
    x_Lot_Serial_tbl => x_Lot_Serial_tbl,
    x_Lot_Serial_val_tbl => x_Lot_Serial_val_tbl,
    x_action_request_tbl => x_action_request_tbl,
    --For bug 3390458
    p_rtrim_data => 'N',
    p_validate_desc_flex => 'Y' -- bug4343612
    COMMIT;
    if x_msg_count > 0 then
    for l_index in 1..x_msg_count loop
    x_msg_data := oe_msg_pub.get(p_msg_index => l_index, p_encoded => F);
    PRINT('x_msg_data: '||x_msg_data);
    end loop;
    end if;
    -- Check the return status
    if x_return_status = FND_API.G_RET_STS_SUCCESS then
    PRINT('success');
    else
    PRINT('failure');
    end if;
    PRINT('x_return_status: '||x_return_status);
    PRINT('x_msg_count: '||x_msg_count);
    PRINT('x_msg_data: '||x_msg_data);
    PRINT('x_header_val_rec: '||x_header_val_rec.accounting_rule);
    PRINT('x_header_rec header_id: ' ||x_header_rec.header_id);
    PRINT('x_header_rec order_number: ' ||x_header_rec.order_number);
    PRINT('x_header_rec ship_to_org_id: ' ||x_header_rec.ship_to_org_id);
    PRINT('x_header_rec payment_term_id: ' ||x_header_rec.payment_term_id);
    PRINT('x_header_rec order_source_id: ' ||x_header_rec.order_source_id);
    PRINT('x_header_rec order_type_id: ' ||x_header_rec.order_type_id);
    PRINT('x_header_rec price_list_id: ' ||x_header_rec.price_list_id);
    PRINT('x_header_rec invoicing_rule_id: ' ||x_header_rec.invoicing_rule_id);
    PRINT('x_header_rec accounting_rule_id: ' ||x_header_rec.accounting_rule_id);
    PRINT('x_header_rec org_id: ' ||x_header_rec.org_id);
    PRINT('x_header_rec sold_to_org_id: ' ||x_header_rec.sold_to_org_id);
    PRINT('x_header_rec invoice_to_org_id: ' ||x_header_rec.invoice_to_org_id);
    PRINT('x_header_rec salesrep_id: ' ||x_header_rec.salesrep_id);
    PRINT('x_header_rec invoice_to_org_id: ' ||x_header_rec.invoice_to_org_id);
    PRINT('x_header_rec operation: ' ||x_header_rec.operation);
    PRINT('x_header_rec transactional_curr_code: ' ||x_header_rec.transactional_curr_code);
    PRINT('x_header_rec orig_sys_document_ref: ' ||x_header_rec.orig_sys_document_ref);
    PRINT('x_header_rec request_date: ' ||x_header_rec.request_date);
    PRINT('x_header_rec conversion_rate_date: ' ||x_header_rec.conversion_rate_date);
    PRINT('x_header_rec last_update_date: ' ||x_header_rec.last_update_date);
    PRINT('x_header_rec ordered_date: ' ||x_header_rec.ordered_date);
    PRINT('x_header_rec creation_date: ' ||x_header_rec.creation_date);
    PRINT('x_header_rec created_by: ' ||x_header_rec.created_by);
    END;
    It is throwing the following Error.
    SQL> exec TEST_PROC;
    x_msg_data: ORA-01403: no data found in Package OE_ORDER_WF_UTIL Procedure
    Create_HdrWorkItem
    x_msg_data: User-Defined Exception in Package OE_ORDER_WF_UTIL Procedure
    Start_HdrProcess
    failure
    x_return_status: U
    x_msg_count: 2
    x_msg_data: User-Defined Exception in Package OE_ORDER_WF_UTIL Procedure
    Start_HdrProcess
    x_header_val_rec: Immediate
    x_header_rec header_id: 156408
    x_header_rec order_number: 64097
    x_header_rec ship_to_org_id: 1425
    x_header_rec payment_term_id: 4
    x_header_rec order_source_id: 0
    x_header_rec order_type_id: 1437
    x_header_rec price_list_id: 1000
    x_header_rec invoicing_rule_id: -2
    x_header_rec accounting_rule_id: 1
    x_header_rec org_id: 204
    x_header_rec sold_to_org_id: 1290
    x_header_rec invoice_to_org_id: 1424
    x_header_rec salesrep_id: 1006
    x_header_rec invoice_to_org_id: 1424
    x_header_rec operation: CREATE
    x_header_rec transactional_curr_code: USD
    x_header_rec orig_sys_document_ref: OE_ORDER_HEADERS_ALL156408
    x_header_rec request_date: 02-APR-09
    x_header_rec conversion_rate_date:
    x_header_rec last_update_date: 02-APR-09
    x_header_rec ordered_date: 02-APR-09
    x_header_rec creation_date: 02-APR-09
    x_header_rec created_by: 13615
    Any help on this would be appreciated.
    I am using R12..

    Hi Nagamohan,
    Thanks for the reply..It was Vision Instance that i was working on..
    There was some problem in setups. I had run the same script on other instance and it is working.
    Before signing off i have one more doubt...
    The script which i used is creating a sales order with booked_flag='Y' but flow_status_code is still 'ENTERED'
    how can i change it to 'BOOKED' using API...
    Thanks for the help...

  • Error -1116 when creating a Sales Order via DI API

    Hi All,
    We have an developed EDI AddOn that creates Sales Orders in SBO 2007 PL13, in one of our clients.
    This AddOn is responsible for the creation up to 100 orders each day on SBO.
    However, sometimes (3 to 4%) during the Sales Order creation, the system return an error -1116 when the Sales Order is created - via oSalesOrder.Add() method.
    The problem is that the order is created anyway, although this error is raised.
    I've searched in the forums and it seems the solution is somehow related with SBO transactions.
    However, the AddOn only created the Sales Order, nothing more.
    Does any body know a solution for this problem?
    Regards,
    Manuel Dias

    Hi,
    see this links,
    Error -1116 when creating delivery note
    Could not commit transaction, ReturnCode:-1116
    Regards,
    siva

Maybe you are looking for