Sales order CIF performance

Hello SCM experts,
We are trying to CIF initial load of sales orders for 2 materials; Each material has Variant configuration. There are 25 APO relevant VC characteristics for each material.
Therefore, total volume of VC materials = 2
Each material has 30,000 sales orders per month.
We are trying to integrate sales orders to SCM 7.0 version; Total volume of sales orders is 100,000 for the Initial load.
Currently, the performance of this integration is worse and takes around 20 hours.
I want to know of any other clients that have good sales order volumes.
Has anyone seen a sales order volume of 100,000 with Variant configuration? What is the best performance that should be expected for this volume?
Appreciate any inputs.

Hi Louis,
Have you considered uses of parallel processing while activating initial load integration model?
I think by processing SOs in parallel processes, it will definitely improve performance.
Please let us know your latest situation.
Regards,
Abhay Kapase

Similar Messages

  • How to bring in the Open Sales Orders while performing Sales Order Conv

    Hi,
    Could you give some suggestions on the below:
    How to bring in the Open Sales Orders while performing Sales Order Conversion in R12.
    Thanks
    Pravin

    See http://ramugvs.wordpress.com/2011/08/27/how-to-stage-and-import-an-order-using-order-import-api-apps-wms-ebiz-11i-r12/
    Sandeep Gandhi

  • Problem with Sales Order CIF IM-job running longer

    We have CIF integratiom Model generation(RIMODGEN) and activation(RIMODAC2) jobs
    running everyday in sequence.
    One of the jobs is for Sales Order Generation
    and activation. The activation job used to take 30-40 seconds earlier(since last
    1 year) but for the last month the job has been taking a lot of time to
    complete. And that too intermittently. On some days the job completes in 30-40
    seconds but on some it takes more than 3000 seconds(and still doesnt complete-
    eventually we mark it successful manually to let successor jobs to start).
    When we analysed the log for this job transfer in SLG1 we found out that
    during activation of this Integration Model, not only Sales Orders pertaining to
    new materials(that would have been added within the day between last IM
    generation job and current IM generation job) were getting transferred. But
    Sales orders pertaining to Materials(which have been active since a number of
    days) were also getting transferred. Ideally, any changes/new Sales orders
    pertaining to these older materials(which were already in an active integration
    model) should have been transferred real time and should not have waited to be
    transferred during the IM activation job.
    We have also noticed that for
    some Sales Olders(for which the materials were already active for long) and
    there has been NO change in the Sales Orders are also getting transferred
    throguh our IM activation job.
    The mesage that we see in the log for
    these Sales Order is shown below:
    Source system:XXXXXX user: RSP100
    transaction CFM2 T_SLS 0001119 function module: /SAPAPO/CIF_XXXXX (As far as I
    understand CFM2 T_SLS* prefix is for Sales Order transfer happen during IM
    activation job)
    "Customer Requirement N BM 0001223200 00010 0001: Method
    changed from N to G"
    "Customer Requirement 0001223200: Requirement adopted
    in APO"

    Is the full name of the directory where you have your source code Documents and Settings as in Win2k or WinXP. In that case, move the source code to a different directory(you might like to create a separate directory). Note that the directory name should not have spaces in it. Try and see what you get.

  • VMI Sales Order CIF to APO

    Dear All;
    We are creating a VMI Order in APO which is CIF'ed to R/3 and a corresponding Sales Order is created with "Z" order type which has been configured.
    But this order is not CIF'ed back to APO. The integration model is active with the material and plant.
    Could you please shed some on light on any missing config here ?
    Thanks
    Vathsan

    Hi Vathsan,
    1) Check is there any struck queues
    2) Check the publication settings under distribution
    definition are maintained in APO customisation
    3) Run /sapapo/ccr for sales order and check the
    error noticed
    Regards
    R. Senthil Mareeswaran.

  • Extract Sales order doc  - performance issue

    Dear all,
    I need to extract SO# and SO line item. The only filtering key that i have right now is:
        Sold-to party number -> from SO header
    By looking at it, I CAN NOT select whole VBAK then scan VBPA order by order.
    Hence I explore the possibility by taking the SO# from VBPA, where at first i get the SO# from this table by using Sold-to party number for data filtering.
    But too bad that, VBPA table key fileds are :
    1. SO#,
    2. SO item #,
    3. Partner function
    For my case, i can only fullfill 3rd key field Partner function. So my VBPA selection is also taking long runtime to perform extraction.
    I need your advice on how should i go about it to solve the performance problem.
    Thanks in advance.

    Hi
    As you have only one filter KUNNR performance will be a issue..
    1 Way... ==> VBAK then VBAP
    2nd Way ==>
    KNVV-KUNNR
    get
    VKORG
    VTWEG
    SPART ( Depends on the configuration there... if for one customer there will be same VKORG VTWEG SPART then u can write READ or Select Single)
    Pass it to VBAK... and then go to VBAP...
    It will not gonna improve much but may be it will improve...
    or else You can go for creating secondary index... but for just satistying one requirement it's not a good idea to create secondary index...
    Also discuss with Functional Consultant if they can give you some more fields in selection screen.. like S.O, Creation Date Range Sales Office Sales Org Division etc etc...
    Hope it will solve your problem..
    Thanks & Regards
    ilesh 24x7
    ilesh Nandaniya
    Thanks & Regards
    ilesh 24x7
    ilesh Nandaniya

  • Sales & Order report performance is too slow!

    Hi All,
    Sales report is prety slow.It took 90% in OLAP time. I tried RSRT all the possible ways & also created OLAP fill query level also but No result. Please help me.
    Thanks
    Vasu.

    Hi Vasu,
    CAN You please refer below link
    http://wiki.sdn.sap.com/wiki/display/BI/HowtoImproveQueryPerformance-A+Checklist
    it tells explains how you can improve your query performace.
    Also as i told since you are FETCHING DATA direct from MASTER data report will be bit slow so try to get data directly from cube and may be u can use filters also.
    Hope this may help you.
    Regards
    Nilesh

  • WBS element in Sales order

    Dear Friends,
    We have an issue as explained below.
    An end user has created a Sales order and added a line Item. He forgot to add WBS Element and continued with delivery. Delivery document has been created without WBS element(Table LIPS is updated without WBS). Before Creating an Invoice end user added WBS element in the sales order and performed Invoicing. When we do Revenue recognition w.r.t a delivery document WBS element is empty because it was not updated.
    We are using F2 billing type and process is Delivery related billing. Issue is how system updated WBS element from the Sales order to Invoice when we are performing Delivery related billing.Is there any setting we can control this action.
    Please suggest.
    with regards,
    Dayanand

    Hi Dayananda
    Check in transaction VTFL for given item category what copying routine are set. Check those copy routine and see if there is any data is being copied from table VBAP
    Similar to above also check transaction VTFA for copying routine (if any)
    As a standard SAP even we create an invoice with reference to the delivery document, still there are some data which is being copied from a sales order i.e. all pricing relevant information is copied from your sales order and not from delivery.

  • ATP check in the Sale order Processing and CO06 transaction (Confirm Qty)

    Hi All,
    While creating the Sale order, After performing the ATP check and saving the document i have called an user exit to make the confirmed Quantity equal to ZERO when the delivery block is set (As requested by customer). That is working fine...
    But the same confirmed Quantity of ZERO is not reflecting in CO06 transaction. Its showing the old value that the value before setting the delivery block.
    I have identified the table VBBE-VMENG which stores the confirmed quantity in CO06 transaction...
    Could you please help me know any USER EXITS or any other solution to change the confirmed quantity to ZERO in CO06 transaction also while delivery block is set in the sale order.
    Thanks &Regards,
    Navaneeth

    Hi All,
    Please help me by providing some clues on this issue...
    Regards,
    Navaneeth

  • Deleting Sales Order Details using BAPI_SALESORDER_CHANGE And Reinserting

    Hi All,
    I need to <b>change a Sales Order</b> in such a way that I would <b>delete all the existing Line Items</b> of that SO And <b>then reinsert new Line Items</b> as generally is the practice of saving a document.(Update Header-Delete Old Item Entries-Reinsert New Present Entries).
    I coded a small test program in ABAP using the <b>BAPI_SALESORDER_GETLIST And BAPI_SALESORDER_CHANGE</b>.
    In order to affect the Qty I have to update the Schedule Parameter also of the BAPI_SALESORDER_CHANGE Function.But this causes a new entry in VBEP.
    eg:
    <b>Before BAPI Calls</b>
    SO-Number:9001
    Header:9001,etc......
    Detail:ItemNo=10,Material=xyz,TargetQty=100,etc..
    Scedule:ItemNo=10,Scheduleline=1,Req_Qty=100,etc...
    I coded the program such that
    1.I <b>Get the List of Items</b> using BAPI_SALESORDER_GETLIST.
    2.Call the <b>BAPI_SALESORDER_CHANGE</b> filling appropraite   values in Parameters <b>with UpdateFlag = 'D'</b>
    3.<b>Insert new values</b> in OrderItems And Schedule Parameters
    say:
    Detail:ItemNo=10,Material=xyz,TargetQty=25,etc..
    Scedule:ItemNo=10,Scheduleline=1,Req_Qty=25,etc...
    4.<b>Call the BAPI_SALESORDER_CHANGE</b> filling appropraite values in Parameters <b>with UpdateFlag = 'I'</b>
    <b>The output now becomes.</b>Header:9001,etc......
    Detail:ItemNo=10,Material=xyz,TargetQty=100,etc..
    Scedule:ItemNo=10,Scheduleline=1,Req_Qty=100,etc...
    ItemNo=10,Scheduleline=2,Req_Qty=25,etc...
    Now After Commit when I see my <b>SO it shows me a qty of
    125</b>.
    I am attaching the code for your analysis.
    Thanx in advance.
    *& Report  ZSM_CHANGESALESORDER                                        *
    REPORT  ZSM_CHANGESALESORDER                    .
    DATA:
    For Calling the GetList BAPI Function
      CUSTOMER_NUMBER LIKE  BAPI1007-CUSTOMER,
      SALES_ORGANIZATION LIKE  BAPIORDERS-SALES_ORG,
      IT_SALES_ORDERS LIKE TABLE OF BAPIORDERS,
      WA_SALES_ORDERS LIKE LINE OF IT_SALES_ORDERS,
      IT_RETURN LIKE TABLE OF BAPIRETURN,
      WA_RETURN LIKE LINE OF IT_RETURN.
    For Calling the ChangeFromData BAPI Function
    DATA:
      SALESDOCUMENT LIKE  BAPIVBELN-VBELN,
      WA_ORDER_HEADER_IN LIKE  BAPISDH1,
      WA_ORDER_HEADER_INX LIKE BAPISDH1X,
      IT_ORDER_ITEM_IN LIKE TABLE OF BAPISDITM ,
      WA_ORDER_ITEM_IN LIKE LINE OF IT_ORDER_ITEM_IN,
      IT_ORDER_ITEM_INX LIKE TABLE OF BAPISDITMX ,
      WA_ORDER_ITEM_INX LIKE LINE OF IT_ORDER_ITEM_INX,
      IT_SCHEDULE_LINES LIKE TABLE OF BAPISCHDL ,
      WA_SCHEDULE_LINES LIKE LINE OF IT_SCHEDULE_LINES,
      IT_SCHEDULE_LINESX LIKE TABLE OF BAPISCHDLX ,
      WA_SCHEDULE_LINESX LIKE LINE OF IT_SCHEDULE_LINESX,
      IT_RETURN_CHG LIKE TABLE OF BAPIRET2,
      WA_RETURN_CHG LIKE LINE OF IT_RETURN_CHG.
    DATA:
      IT_RETURN_CT LIKE BAPIRET2.
    PARAMETERS:
      P_SO LIKE VBAK-VBELN,
      P_CUSTNO LIKE  BAPI1007-CUSTOMER,
      P_SORG LIKE BAPIORDERS-SALES_ORG.
    START-OF-SELECTION.
      SALESDOCUMENT = P_SO.
      CUSTOMER_NUMBER = P_CUSTNO.
      SALES_ORGANIZATION = P_SORG.
    Retrieve the Existing Sales Order details for that Sales Order.
      PERFORM GETREQSODETAILS.
    Delete the Existing Sales Order details from that Sales Order.
      PERFORM DELETEOLDSODETAILS.
    Insert New details for that Sales Order.
       PERFORM ADDNEWSODETAILS.
    END-OF-SELECTION.
      PERFORM COMMITTRANS.
    *&      Form  GetReqSODetails
    FORM GETREQSODETAILS .
      CALL FUNCTION 'BAPI_SALESORDER_GETLIST'
        EXPORTING
          CUSTOMER_NUMBER    = CUSTOMER_NUMBER
          SALES_ORGANIZATION = SALES_ORGANIZATION
        IMPORTING
          RETURN             = WA_RETURN
        TABLES
          SALES_ORDERS       = IT_SALES_ORDERS.
    *delete the Sales Order Details of Sales Orders other than the req.One
      IF NOT IT_SALES_ORDERS[] IS INITIAL.
        SORT IT_SALES_ORDERS BY SD_DOC.
        LOOP AT IT_SALES_ORDERS INTO WA_SALES_ORDERS.
          IF WA_SALES_ORDERS-SD_DOC NE SALESDOCUMENT.
            DELETE IT_SALES_ORDERS.
          ENDIF.
        ENDLOOP.
      ENDIF.
    ENDFORM.                    " GetReqSODetails
    *&      Form  deleteOldSODetails
    FORM DELETEOLDSODETAILS .
      DATA: IRECCOUNT TYPE I.
      IRECCOUNT = 1.
    *Clear all the Inernal Tables And Work Areas
    *and Update the SO Header Index
      PERFORM CLEARDATA.
      PERFORM SOHEADERINDEX.
      LOOP AT IT_SALES_ORDERS INTO WA_SALES_ORDERS.
    *Fill the Order Details Index Internal Table
        PERFORM FILLSODELETEDTLS_INDEX_PARAM
        USING WA_SALES_ORDERS-ITM_NUMBER 'D'.
    *Fill the Order Scedule Index Internal Table
        PERFORM FILLSODELETESCH_INDEX_PARAM
        USING WA_SALES_ORDERS-ITM_NUMBER IRECCOUNT 'D'.
      ENDLOOP.
    *call the Sales Order Change Fumction to delete the Existing Data
      CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
        EXPORTING
          SALESDOCUMENT    = SALESDOCUMENT
          ORDER_HEADER_INX = WA_ORDER_HEADER_INX
        TABLES
          RETURN           = IT_RETURN_CHG
          ORDER_ITEM_INX   = IT_ORDER_ITEM_INX
          SCHEDULE_LINESX  = IT_SCHEDULE_LINESX.
    ENDFORM.                    " deleteOldSODetails
    *&      Form  SOHeaderIndex
    FORM SOHEADERINDEX .
      WA_ORDER_HEADER_INX-UPDATEFLAG = 'U'.
    ENDFORM.                    " SOHeaderIndex
    *&      Form  FillSODeleteDtls_Index_param
    FORM FILLSODELETEDTLS_INDEX_PARAM
    USING VALUE(P_ITM_NUMBER) VALUE(P_FLAG).
      WA_ORDER_ITEM_INX-ITM_NUMBER = P_ITM_NUMBER.
      WA_ORDER_ITEM_INX-UPDATEFLAG = P_FLAG.
      APPEND WA_ORDER_ITEM_INX TO IT_ORDER_ITEM_INX.
    ENDFORM.                    " FillSODeleteDtls_Index_param
    *&      Form  FILLSODELETEsch_Index_PARAM
    FORM FILLSODELETESCH_INDEX_PARAM
    USING VALUE(P_ITM_NUMBER) VALUE(P_RECCOUNT) VALUE(P_FLAG).
      WA_SCHEDULE_LINESX-ITM_NUMBER = P_ITM_NUMBER.
      WA_SCHEDULE_LINESX-SCHED_LINE = P_RECCOUNT.
      WA_SCHEDULE_LINESX-UPDATEFLAG = P_FLAG.
      APPEND WA_SCHEDULE_LINESX TO IT_SCHEDULE_LINESX.
    ENDFORM.                    " FILLSODELETEsch_Index_PARAM
    *&      Form  addnewSODETAILS
    FORM ADDNEWSODETAILS .
      DATA: IRECCOUNT TYPE I, ITEMNO TYPE I.
      IRECCOUNT = 1.
    *Clear all the Inernal Tables And Work Areas
    *and Update the SO Header Index
      PERFORM CLEARDATA.
      PERFORM SOHEADERINDEX.
      WHILE IRECCOUNT <= 1.
        ITEMNO = IRECCOUNT * 10.
    *Fill the New Order Details in the Internal Table
        PERFORM FILLSODTLDATA USING ITEMNO 'TEST FG' 37 .
    *Fill the Order Details Index Internal Table
        PERFORM FILLSODELETEDTLS_INDEX_PARAM USING ITEMNO 'I'.
    *Fill the New Schedule Details in the Internal Table
        PERFORM FILLSOSCHDATA USING ITEMNO IRECCOUNT 37 .
    *Fill the Order Scedule Index Internal Table
        PERFORM FILLSODELETESCH_INDEX_PARAM
        USING ITEMNO IRECCOUNT 'I'.
        IRECCOUNT = IRECCOUNT + 1.
      ENDWHILE.
    *call the Sales Order Change Fumction to Insert New Data
      CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
        EXPORTING
          SALESDOCUMENT    = SALESDOCUMENT
          ORDER_HEADER_INX = WA_ORDER_HEADER_INX
        TABLES
          RETURN           = IT_RETURN_CHG
          ORDER_ITEM_IN    = IT_ORDER_ITEM_IN
          ORDER_ITEM_INX   = IT_ORDER_ITEM_INX
          SCHEDULE_LINES   = IT_SCHEDULE_LINES
          SCHEDULE_LINESX  = IT_SCHEDULE_LINESX.
    ENDFORM.                    " addnewSODETAILS
    *&      Form  clearData
    FORM CLEARDATA .
      CLEAR WA_ORDER_HEADER_INX.
      CLEAR WA_ORDER_ITEM_INX.
      REFRESH IT_ORDER_ITEM_INX.
      CLEAR WA_SCHEDULE_LINESX.
      REFRESH IT_SCHEDULE_LINESX.
      CLEAR WA_RETURN.
      REFRESH IT_RETURN.
      CLEAR WA_ORDER_ITEM_IN.
      REFRESH IT_ORDER_ITEM_IN.
      CLEAR WA_SCHEDULE_LINES.
      REFRESH IT_SCHEDULE_LINES.
    ENDFORM.                    " clearData
    *&      Form  FILLSODTLDATA
    FORM FILLSODTLDATA  USING    VALUE(P_ITEMNO) VALUE(P_MATERIAL)
    VALUE(P_TARGET_QTY) .
      WA_ORDER_ITEM_IN-ITM_NUMBER = P_ITEMNO.
      WA_ORDER_ITEM_IN-MATERIAL = P_MATERIAL.
      WA_ORDER_ITEM_IN-TARGET_QTY = P_TARGET_QTY.
      APPEND WA_ORDER_ITEM_IN TO IT_ORDER_ITEM_IN.
    ENDFORM.                    " FILLSODTLDATA
    *&      Form  FILLSOschDATA
    FORM FILLSOSCHDATA  USING    VALUE(P_ITEMNO)
                                 VALUE(P_RECCOUNT)
                                 VALUE(P_REQ_QTY)  .
      WA_SCHEDULE_LINES-ITM_NUMBER = P_ITEMNO.
      WA_SCHEDULE_LINES-SCHED_LINE = P_RECCOUNT.
      WA_SCHEDULE_LINES-REQ_QTY = P_REQ_QTY.
      APPEND WA_SCHEDULE_LINES TO IT_SCHEDULE_LINES.
    ENDFORM.                    " FILLSOschDATA
    *&      Form  committrans
    FORM COMMITTRANS .
      DATA:SUCCESSFLAG(1).
      LOOP AT IT_RETURN_CHG INTO WA_RETURN_CHG.
        IF WA_RETURN_CHG-TYPE = 'S'
              AND WA_RETURN_CHG-ID = 'V1'
              AND WA_RETURN_CHG-NUMBER = 311
              AND SUCCESSFLAG IS INITIAL.
          CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
            EXPORTING
              WAIT   = 'X'
            IMPORTING
              RETURN = IT_RETURN_CT.
          SUCCESSFLAG = 'X'.
        ENDIF.
      ENDLOOP.
      IF SUCCESSFLAG IS INITIAL.
        WRITE: 'SORRY SOME ERROR'.
      ELSE.
        WRITE: 'SUCCESSFUL'.
      ENDIF.
    ENDFORM.                    " committrans

    Thanx wolfgang,
    I needed that info.
    As I had mentioned in the earlier posts, I want to delete the old Sales Order Item Details,
    Schedule Details,Basic Price data And Reinsert data in the same.
    I am giving u the algo that I have used.
    1.<b>Get the SalesOrder Details</b> for a particular Sales Order using BAPI_SALESORDER_GETLIST(para:customer & sales Org and then deleting unwanted SO data).
    2.<b>Delete</b> the Sales Order <b>Item Details,Schedule Details</b> using BAPI_SALESORDER_CHANGE.
    3.<b>Commit</b> Transaction(<b>If I dont use this commit Error comes in Step No.7 while Commiting</b>)
    using BAPI_TRANSACTION_COMMIT.
    4.Check <b>Return Table</b> of both BAPI_SALESORDER_CHANGE and BAPI_TRANSACTION_COMMIT.
    5.if Step No.4 is <b>Not okay</b> <b>then Rollback</b>(BAPI_TRANSACTION_TRANSACTIN) <b>and Exit</b> <b>else move to step 6</b>.
    6.<b>Add New</b> Sales Order <b>Item Details,Schedule Details, Basic Price</b> using BAPI_SALESORDER_CHANGE.
    7.<b>Commit Transaction</b> using BAPI_TRANSACTION_COMMIT.
    8.<b>Check Return</b> Log of both BAPI_SALESORDER_CHANGE and BAPI_TRANSACTION_COMMIT.
    9.if Step No.9 is okay then Exit else Rollback(BAPI_TRANSACTION_TRANSACTIN) and move to step 10.
    10.Add Old Sales Order Item Details,Schedule Details, Basic Price from Data available in Internal
    table(Filled in step.1 ) using BAPI_SALESORDER_CHANGE.
    11.Commit Transaction using BAPI_TRANSACTION_COMMIT.
         This <b>works fine in 1 server in which I get the message of Incomplete Data,etc...when I make a Sales Order from va01</b>.
    But in another server where I dont this message,I get <b>error in step  7 or 11 as per the flow</b>.
    The return structure of BAPI_TRANSACTION_COMMIT contains error with Message 'Updating was not possible'. Also the message 'Updation was terminated' cms frm the SAP server.  
         What could be the reason?
    Thanx in advance

  • Schema determination in sales order for external services

    Hi,
    I've created a maintenance order including two services into operation 10
    (control key PM03). The pricing log in the order shows that the system
    uses schema ZS0001. After releasing it, the purchase requisition (class
    ZMS1) is created. When the PO is created (class ZMS2) via requisition
    assignment list (ME58), the schema is changed to RM0000, despite of the
    fact that table T165A contains the following entries:
    Doc cat. Doc Type Procedure
    B ZMS1 ZS0001
    B ZMS2 ZS0001
    F ZMS1 ZS0001
    F ZMS2 ZS0001
    I would need to keep the schema to ZS0001 in the sales order to perform
    the right price determination.
    Any help? Many thanks.

    Hi
    T165A is used for 'Services Pricing'.
    Please note that for Services PO, you will have two pricing schema.
    1) At PO-Item Level : RM0000 (or whatever you define in schema determination in Purchasing ->Conditions IMG and assign in your vendor master)
    2) At service line level : Based on settings in T165A.
    If you check in Services level conditions screen and click on Analysis, you will find that ZS0001 is triggered.
    Best regards
    Ramki

  • Creating Sales order texts while using BDC session method is not working

    Hi All,
    I have an existing program which creates sales order using BDC session method.( Actual program uses BAPI to create sales order and in case if any error occurs during creation of sales order BDC session is generated so that user can process it later and i am facing issues in this part of code where it uses BDC)
    I wanted to modify this BDC sesion  to update the sales order text also. I tried recording VA01 for creationg sales order text unfortunatly it is not capturing the data i am entering in the text fields.
    Please suggest if there is any way to create sales order using BDC.
    Regards
    Sheeba

    Hi Madhu,
    '=TP_CREATE' is the OK code i am getting for creating TEXTS. But the text entered are not captured in BDC.
    Part of BDC program generated for cretaing sales order texts.
    perform bdc_dynpro      using 'SAPMV45A' '4003'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '=%_GC 128 22'.
    perform bdc_field       using 'LV70T-SPRAS'
                                  'EN'.
    perform bdc_dynpro      using 'SAPMV45A' '4003'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '=TP_CREATE'.
    perform bdc_field       using 'LV70T-SPRAS'
                                  'EN'.
    perform bdc_dynpro      using 'SAPMV45A' '4003'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '=%_GC 128 22'.
    perform bdc_field       using 'LV70T-SPRAS'
                                  'EN'.
    perform bdc_dynpro      using 'SAPMV45A' '4003'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '=TP_CREATE'.
    perform bdc_field       using 'LV70T-SPRAS'
                                  'EN'.
    perform bdc_dynpro      using 'SAPMV45A' '4003'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '/EBACK'.
    perform bdc_field       using 'LV70T-SPRAS'
                                  'EN'.
    perform bdc_dynpro      using 'SAPMV45A' '4001'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '=SICH'.
    Regards,
    Sheeba

  • How sales order number generated in the SAP R/3  is transferred to SAP APO

    Dear Experts,
    During the creation of the Sales order in SAP  R/3 an Purchase requisition is created in SAP APO and assigned with temporary sales order and when we save the sales order in R/3 the corresponding sales order number is attached with the purchase requisition in SAP APO. Is there any exits or BADI available while this Sales order detail transferred to APO or during this sales order details attached to Purchase requisition  in APO side.
    Many thanks in advance,
    Senthil

    Senthil,
    During the creation of the Sales order in SAP R/3 a Purchase requisition is created in SAP APO
    ?? I guess you are talking about one of the planning procedures that executes 'Start product heuristic immediately', yes?
    and assigned with temporary sales order
    I guess you are talking about [Temporary Quantity Assignments|http://help.sap.com/saphelp_glossary/en/74/b171467944d3119b440060b0671acc/content.htm], yes?
    Is there any exits or BADI available while this Sales order detail transferred to APO
    Standard enhancements are
    Sales order CIF enhancement on the ECC side
    CIFSLS03  (outbound from ECC)
    Sales order CIF enhancement on the APO side
    APOCF010 (Inbound from ECC)
    Best Regards,
    DB49

  • Unable to release 800 sales orders at one go in ByD

    Hi,
    We have 800 sales orders which are Preparation status. When we try to release all the 800 sales orders we have experienced system crash/dump twice roughly 11-12 mins into the process. At the end of the processing none of the sales orders got released. Could you please advise how can we release all the 800 sales orders at one go and complete the process without any dumps. Could someone please advise on this?
    Many Thanks,
    Deepthi

    Hi,
    The reason why the 800 sales orders are not releasing at one go is that Release function on sales order is performing ATP checks and it is locating if the products are in place etc., and then after confirming all the checks, it is releasing the sales order. I am exploring the possibility of writing an SDK solution of releasing the sales order without having to perform these checks and perform the checks may be while loading the sales order or may be perform checks separately and then release separately all 800 sales orders at one go. Can someone please advise?
    Kind Regards,
    Deepthi

  • Sales order number not showin in ATP sccreen

    Hello All
                        Can you please answer my quesiton regarding ATP, i created a sales order, system performed ATP check and saved.
    In MD04 screen, i see the sales order number as a demand, but when i navigate to ATP quantities screen from MD04, there i see Totals record demand demand for the sales order, but i can't see the sales order number even when i click on Details of total records, also i am not able to create a delivery for this sales order, can you please tell me how to fix this?
    Thanks
    manju

    Please see the date the Schedule line has been confirmed. Delivery can be created only the material availablility date seen in the shipping tab in Schedule line. or the transportation planning date seen in the shipping tab of schedule line.
    In case if you still have have issues, please reply.
    Regards,
    vasim.

  • Help with SE37 code needed - create sales order

    Hi Guurus,
    Can you please help? I finally finished with function creation (I just adopted the function, which I found in the system and it works ok, YEAH!!!)
    BUT!!! It is working just for the sales order creation with one item.
    Is it a big deal if you adopt my code that the function will have possibility to add more then one item?
    Thanks in advance
    Sašo
    Here is the code:
    *FUNCTION Z_RFC_SD_SIMO_SALES_ORDER2.
    *""Local interface:
    **"  IMPORTING
    **"     VALUE(P_AUART) TYPE  AUART DEFAULT 'zhp'
    **"     VALUE(P_VKORG) TYPE  VKORG DEFAULT 0001
    **"     VALUE(P_VTWEG) TYPE  VTWEG DEFAULT 07
    **"     VALUE(P_SPART) TYPE  SPART DEFAULT 01
    **"     VALUE(P_AUGRU) TYPE  AUGRU DEFAULT 001
    **"     VALUE(P_BSTKD) TYPE  BSTKD DEFAULT 'test si order avtom'
    **"     VALUE(P_SOLD) TYPE  KUNNR DEFAULT 21000069
    **"     VALUE(P_SHIP) TYPE  KUNNR DEFAULT 21000069
    **"     VALUE(P_MATNR) TYPE  MATNR DEFAULT 'SIOBRACUN'
    **"     VALUE(P_MENGE) TYPE  KWMENG DEFAULT 1
    **"     VALUE(P_PLANT) TYPE  WERKS_D DEFAULT 0001
    **"     VALUE(P_ITCAT) TYPE  PSTYV DEFAULT 'ZG2W'
    **"     VALUE(P_LGORT) TYPE  LGORT_D DEFAULT 0001
    **"  EXPORTING
    **"     VALUE(V_VBELN) TYPE  VBELN
    **"     VALUE(RESULT) TYPE  CHAR01
    DATA DECLARATIONS.
    **DATA: v_vbeln LIKE vbak-vbeln.
    *DATA: header LIKE bapisdhead1.
    *DATA: headerx LIKE bapisdhead1x.
    *DATA: item LIKE bapisditem OCCURS 0 WITH HEADER LINE.
    *DATA: itemx LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
    *DATA: partner LIKE bapipartnr OCCURS 0 WITH HEADER LINE.
    *DATA: return LIKE bapiret2 OCCURS 0 WITH HEADER LINE.
    *DATA: lt_schedules_inx TYPE STANDARD TABLE OF bapischdlx
    *WITH HEADER LINE.
    *DATA: lt_schedules_in TYPE STANDARD TABLE OF bapischdl
    *WITH HEADER LINE.
    HEADER DATA
    *header-doc_type = p_auart.
    *headerx-doc_type = 'X'.
    *header-sales_org = p_vkorg.
    *headerx-sales_org = 'X'.
    *header-distr_chan = p_vtweg.
    *headerx-distr_chan = 'X'.
    *header-division = p_spart.
    *headerx-division = 'X'.
    **order reason
    *header-ord_reason = p_augru.
    *headerx-ord_reason = 'X'.
    **PO number from MAX
    *header-PURCH_NO_C = p_BSTKD.
    *headerx-PURCH_NO_C = 'X'.
    *headerx-updateflag = 'I'.
    PARTNER DATA
    *partner-partn_role = 'AG'.
    *partner-partn_numb = p_sold.
    *APPEND partner.
    *partner-partn_role = 'WE'.
    *partner-partn_numb = p_ship.
    *APPEND partner.
    ITEM DATA
    *itemx-updateflag = 'I'.
    *item-itm_number = '000010'.
    *itemx-itm_number = 'X'.
    *item-material = p_matnr.
    *itemx-material = 'X'.
    *item-plant = p_plant.
    *itemx-plant = 'X'.
    *item-target_qty = p_menge.
    *itemx-target_qty = 'X'.
    *item-target_qu = ' '.
    *itemx-target_qu = 'X'.
    *item-item_categ = p_itcat.
    *itemx-item_categ = 'X'.
    **item-STORE_LOC = p_LGORT.
    **itemx-STORE_LOC = 'X'.
    *APPEND item.
    *APPEND itemx.
    Fill schedule lines
    *lt_schedules_in-itm_number = '000010'.
    *lt_schedules_in-sched_line = '0001'.
    *lt_schedules_in-req_qty = p_menge.
    *APPEND lt_schedules_in.
    Fill schedule line flags
    *lt_schedules_inx-itm_number = '000010'.
    *lt_schedules_inx-sched_line = '0001'.
    *lt_schedules_inx-updateflag = 'X'.
    *lt_schedules_inx-req_qty = 'X'.
    *APPEND lt_schedules_inx.
    Call the BAPI
    *CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
    *EXPORTING
    *sales_header_in = header
    *sales_header_inx = headerx
    *IMPORTING
    *salesdocument_ex = v_vbeln
    *TABLES
    *return = return
    *sales_items_in = item
    *sales_items_inx = itemx
    *sales_schedules_in = lt_schedules_in
    *sales_schedules_inx = lt_schedules_inx
    *sales_partners = partner.
    Check the return table.
    *LOOP AT return WHERE type = 'E' OR type = 'A'.
    *EXIT.
    *ENDLOOP.
    *IF sy-subrc = 0.
    *result = 'E'.
    *ELSE.
    *COMMIT WORK AND WAIT.
    *result = 'S'.
    *ENDIF.
    *ENDFUNCTION.
    Edited by: Saso Poljansek on Jan 22, 2008 10:23 AM

    Hi,,
        Include           YCL_CREATE_SALES_DOCU                         *
         Form  salesdocu
         This Subroutine is used to create Sales Order
         -->P_HEADER           Document Header Data
         -->P_HEADERX          Checkbox for Header Data
         -->P_ITEM             Item Data
         -->P_ITEMX            Item Data Checkboxes
         -->P_LT_SCHEDULES_IN  Schedule Line Data
         -->P_LT_SCHEDULES_INX Checkbox Schedule Line Data
         -->P_PARTNER  text    Document Partner
         <--P_w_vbeln  text    Sales Document Number
    DATA:
      lfs_return like line of t_return.
    FORM create_sales_document changing P_HEADER  like fs_header
                                       P_HEADERX like fs_headerx
                                       Pt_ITEM   like t_item[]
                                       Pt_ITEMX  like t_itemx[]
                                       P_LT_SCHEDULES_IN  like t_schedules_in[]
                                       P_LT_SCHEDULES_INX like t_schedules_inx[]
                                       Pt_PARTNER  like t_partner[]
                                       P_w_vbeln  like w_vbeln.
    This Perform is used to fill required data for Sales order creation
      perform sales_fill_data changing p_header
                                       p_headerx
                                       pt_item
                                       pt_itemx
                                       p_lt_schedules_in
                                       p_lt_schedules_inx
                                       pt_partner.
    Function Module to Create Sales and Distribution Document
      perform sales_order_creation using p_header
                                         p_headerx
                                         pt_item
                                         pt_itemx
                                         p_lt_schedules_in
                                         p_lt_schedules_inx
                                         pt_partner.
      perform return_check using p_w_vbeln .
    ENDFORM.                                 " salesdocu
        Form  commit_work
        To execute external commit                                    *
    FORM commit_work .
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
       WAIT          = c_x
    ENDFORM.                                 " Commit_work
    Include ycl_sales_order_header          " To Fill Header data and Item data
    Include ycl_sales_order_header.
         Form  return_check
        To validate the sales order creation
    FORM return_check using pr_vbeln type vbeln.
    if pr_vbeln is initial.
        LOOP AT t_return into lfs_return .
          WRITE / lfs_return-message.
          clear lfs_return.
        ENDLOOP.                             " Loop at return
      else.
        perform commit_work.                 " External Commit
        Refresh t_return.
        fs_disp-text = text-003.
        fs_disp-number = pr_vbeln.
        append fs_disp to it_disp.
      if p_del eq c_x or p_torder eq c_x or
        p_pgi eq c_x or p_bill eq c_x.
        perform delivery_creation.           " Delivery order creation
        endif.                               " If p_del eq 'X'......
      endif.                                 " If p_w_vbeln is initial
    ENDFORM.                                 " Return_check
    *&      Form  sales_order_creation
          text
         -->P_P_HEADER  text
         -->P_P_HEADERX  text
         -->P_PT_ITEM  text
         -->P_PT_ITEMX  text
         -->P_P_LT_SCHEDULES_IN  text
         -->P_P_LT_SCHEDULES_INX  text
         -->P_PT_PARTNER  text
    FORM sales_order_creation  USING    P_P_HEADER like fs_header
                                        P_P_HEADERX like fs_headerx
                                        P_PT_ITEM like t_item[]
                                        P_PT_ITEMX like t_itemx[]
                                        P_P_LT_SCHEDULES_IN like t_schedules_in[]
                                        P_P_LT_SCHEDULES_INX like t_schedules_inx[]
                                        P_PT_PARTNER like t_partner[].
        CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
        EXPORTING
          sales_header_in     = p_p_header
          sales_header_inx    = p_p_headerx
        IMPORTING
          salesdocument_ex    = w_vbeln
        TABLES
          return              = t_return
          sales_items_in      = p_pt_item
          sales_items_inx     = p_pt_itemx
          sales_schedules_in  = p_p_lt_schedules_in
          sales_schedules_inx = p_p_lt_schedules_inx
          sales_partners      = p_pt_partner.
    ENDFORM.                    " sales_order_creation
    this is code to create sales document
    plzz reward if it is usefull...
    plzz dont forget to reward......

Maybe you are looking for