Steps to create Collective delivery

Hi,
Someone pl tell me steps to create collective delivery
Thanks Munna

hi,
You can schedule delivery creation for whenever you like using automatic background processing.
Procedure
To plan background processing for delivery creation, proceed as follows:
1.Either apply a user role for background processing or make a copy of a user role for shipment due processing for yourself.
During the test phase, use a function code profile for shipment due list display within this user role.
2.Test the shipment due processing with this user role until you only need to execute the Create delivery in background function after the shipment due list is first displayed in order to ship part of the delivery list. (Vary the rules for line selection or for quantity definition during item processing, for instance.)
3.Change the function code profile in the user role from Display to Deliver.
4.From Logistics ® Logistics Execution ® Outbound Process ® Goods Issue for Outbound Delivery, choose Outbound Delivery ® Create ® Collective Processing of Documents Due for Delivery ® Delivery scenario of your choice.
5.Choose the user role that you want to use for background scheduling in the User role field on the User role tab page.
6.Enter additional selection parameters on the selection screen.
7.Save the selection screen as a variant.
8.From shipping, choose Outbound delivery ® Create ® Collective Processing of Documents Due for Delivery ® Plan Background Processing and execute the delivery scenario for background planning.
9.Choose the selection variant you want and then select Schedule job.
10.Follow the basis dialog for scheduling a background job.
regards
sadhu kishore

Similar Messages

  • Step for creating inbound delivery in case of customer return.

    Hi,
    When I start vl31N I can create with reference to vendor or PO an inbound delivery.
    How to create inbound delivery with reference to a customer return?
    What to do?
    Thank you in advance,
    Eric van Zundert.

    Hi,
    You can try to create a copy control for return sales order to inbound delivery document. Depending on business requirements like combining vendor PO and returns sales orders, you can try to use VL31N.
    If it is only returns sales orders that needs to be processed, then SAP standard document types and its associated copy control would help.
    Regards
    P.S: Does your scenario relate to import process? I am in the same boat.
    Edited by: Shiva Ram on Jan 22, 2008 2:17 PM

  • SD create Collective delivery document against scheduling agreement.

    Dear freinds,
    I have created  scheduling agreements for single material , and updated forecast deliery agaisnt IDOCS,
    now I want to make a single delivery agaisnt four different materials.
    I use Transaction VL 10 for Delivery due list and  selected diff. materials four items,executed  backgroud run,
    system is creating two delivery documents instead of one.
    Please advise me how to get single delivery document against multiple delivery due items.
    in customer master i marked to order combination, partial delivery allowed up to 9 deliveries
    Regards
    Dilip

    Excellent information !
    I understood what you have mentioned .
    Just I need your clarifications for my below queries to fix this issue .
    There are 6 line items in this scheduling agreement .
    For 3 line items , delivery schedule date is 02/08/2008 . for another 2 line items, delivery schedule is 05/07/2008 . due to this different delivery schedules for line items  in scheduling agreement . whenever  user creates delivery , delivery split is happening .
    In order to avoid this problem , can ask user to change delivery schedule for another 2 line items to 02/08/2008 from 05/07/2008 . ?
    If user change this delivery schedule  for this line items , is there any ramification in anyway ?.
    Thanks In Advance

  • Collective Delivery Vs Group Delivery and detail steps

    Hi, I am new here so apologies if i post something that doesnt belong here. i know there are posts on this topic, however i wanted to have a bit more precised description on this. so i will appreciate if someone can explain it to me.
    1. Is Collective delivery = Group delivery?
    2. Can Collective / group delivery be done for different sold to, ship to parties, different material, delivery date and shipping points? If yes can somebody plz give me detail steps?
    How to process one delivery for multiple sales orders ? (both with same sold to ship to, material, shp point and with different ones)
    How can billing be processed when one delivery is created for many orders?
    3. How collective / group delivery processed in back ground and upfront? also in batch? will appreciate steps plz.
    4. How does "variant" works in delivery creation? the word is Variant is confusing here for me.
    Thanks.

    Hi SAP SD,
    U r correct, U did partial delivery that's the reason document flow show's u delvery is in process.
    Once all order quantity will deliver it shows status full.
    Reward if it helpful.
    Regards
    Sasikanth.Ch

  • How to create one delivery for multiple sales order

    Hi!! Friends,
    Can some one explain the steps to be followed in creating one delivery for multiple sales order in SAP SD.
    Regards
    AKASH
    Message was edited by:
            AKASH TAMBI

    Hi.,
                  You can combine different orders in to one delivery ,But for the customer Order combination should be checked in  the sales area data of the shipping tab,we can combine orders but the ship to party,Route,Inco terms,Shipping date,shipping point should be same,you can do in T.code VL04 & VL10
    REWARD if helpfull
    Thanks & Regards
    Narayana

  • ABAP dump(SAPSQL_ARRAY_INSERT_DUPREC) while creating a delivery

    Hello Friends,
    I am getting the dump while creating the delivery .The error details are as follows.
    The ABAP/4 Open SQL array insert results in duplicate database record
    What happened?
    The current ABAP/4 program "SAPLV05I " had to be terminated because
    one of the statements could not be executed.
    How to correct the error
    Use an ABAP/4 Open SQL array insert only if you are sure that none of
    the records passed already exists in the database.
    If the error occurred in a non-modified SAP program, you may be
    able to find a solution in the SAP note system.
    If you have access to the note system yourself, use the following
    search criteria:
    "SAPSQL_ARRAY_INSERT_DUPREC"
    "SAPLV05I " or "LV05IU15 "
    "SD_PARTNER_UPDATE"
    Source code extract
    004500                                           POSNR = I_XVBPA-POSNR
    004510                                           PARVW = I_XVBPA-PARVW.
    004520               IF I_YVBPA-STCD1 <> I_XVBPA-STCD1 OR
    004530                   I_YVBPA-STCD2 <> I_XVBPA-STCD2 OR
    004540                   I_YVBPA-STCD3 <> I_XVBPA-STCD3 OR
    004550                   I_YVBPA-STCD4 <> I_XVBPA-STCD4 OR
    004560                   I_YVBPA-STCDT <> I_XVBPA-STCDT OR
    004570                   I_YVBPA-STKZN <> I_XVBPA-STKZN OR
    004580                   I_YVBPA-J_1KFREPRE <> I_XVBPA-J_1KFREPRE OR
    004590                   I_YVBPA-J_1KFTBUS <> I_XVBPA-J_1KFTBUS OR
    004600                   I_YVBPA-J_1KFTIND <> I_XVBPA-J_1KFTIND.
    004610                 MOVE-CORRESPONDING I_XVBPA TO WA_XVBPA3I.
    004620                 APPEND WA_XVBPA3I TO DA_XVBPA3I.
    004630               ENDIF.
    004640             ENDIF.
    004650           ENDIF.
    004660         WHEN UPDKZ_OLD.
    004670           IF DA_VBPA-ADRDA CA GCF_ADDR_IND_COMB_MAN_OLD   OR
    004680              DA_VBPA-ADRDA CA GCF_ADDR_IND_COMB_MAN_ADRC.
    004690             YADR-ADRNR = DA_VBPA-ADRNR. COLLECT YADR.
    004700           ENDIF.
    004710           IF DA_VBPA-ADRDA CA GCF_ADDR_IND_COMB_MAN_OLD   OR
    004720              DA_VBPA-ADRDA CA GCF_ADDR_IND_COMB_MAN_ADRC.
    004730             XADR-ADRNR = DA_VBPA-ADRNR. COLLECT XADR.
    004740           ENDIF.
    004750       ENDCASE.
    004760     ENDLOOP.
    004770     UPDATE (OBJECT) FROM TABLE DA_XVBPAU.
    004780     UPDATE VBPA3 FROM TABLE DA_XVBPA3U.
    004790
         >     INSERT (OBJECT) FROM TABLE DA_XVBPAI.
    004810     INSERT VBPA3 FROM TABLE DA_XVBPA3I.
    004820
    004830     IF SY-SUBRC > 0.
    Could you please suggest me ,what could be the reason for dump and how to avoid dump?
    <REMOVED BY MODERATOR>
    Thank you in advance,
    Arvind.
    Edited by: Alvaro Tejada Galindo on Apr 22, 2008 5:16 PM
    Edited by: Alvaro Tejada Galindo on Apr 22, 2008 5:16 PM

    Hello, I have very same error
    Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
    Exception              CX_SY_OPEN_SQL_DB
    Transaction......... "VL01N "                                                                
    Program............. "SAPLV05I"                                                              
    Screen.............. "RSM13000 3000"                                                         
    Screen line......... 2   
    SAP kernel....... 700  
    Patch level. 75 
    Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"                             
    SAP database version. 700                                                                    
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2" 
    The ABAP/4 Open SQL array insert results in duplicate database records.
    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught  in procedure "SD_PARTNER_UPDATE" "(FUNCTION)", nor was it propagated by a RAISING clause.
    I use SAP_APPL SAPKH60006 Support Package
    The NUMBER RANGE OBJECT HAS NO ERRORS!
    I went trough the zillions of notes all of them affect the old releases.... Please advice.
    Patiently yours,
    SAP User

  • Creating inbound delivery without reference to PO - from inbound idoc

    Hi guys,
    I have a scenario wherein I need to create inbound delivery from inbound Idoc from external system without reference of PO. There is no PO created in SAP and this inbound delivery will be used just to receive material (purely for logistic purpose).
    I have identified DELVRY03 or 05 as Idoc type but I am not sure whether system will create inbound delivery without having reference PO. I have two questions here -
    1. Can we create inbound delivery without reference to PO?
    2. If yes, which Idoc type should I use to create such inbound delivery?
    Please help.
    Thanks,
    Parimal.

    Dear Parimal,
    In standard, An inbound delivery can be created as follows:
    With reference to a purchase order
    With collective processing for several purchase orders
    With reference to a stock transport order
    With reference to a customer return

  • Does item category TAS allow to create Outbound delivery doc?

    Hi experts,
    I have a problem with the delivery creation.  The scenario is:
    Our vendor missed to deliver a part to us. Say for example he missed to delivery the screw (used to adjust the time) in the wrist watch. This part is supposed to be assembled together with the wrist watch & delivered to our customer.
    Now we need to deliver this missed part to our customer. The initial watch has been shipped to the customer without the screw. But the cost of the screw is already included in the total cost of the watch.
    Now the vendor is going to send us this screw.  So my requirement is to create a subsequent free of charge kind of sales order that triggers a PR to the vendor & once this PR is converted to PO, on the PO
    the Free Item will be ticked as the Vendor charged us for the whole wrist watch. This is also a kind of subsequent free of charge delivery by the vendor.
    When I use item category TAS it does generates the PR & I converted this to a PO to this vendor. I also did the GR for this PO.  But when I create outbound delivery for this subsequent free of charge sales order,
    it says the item is not relevant for delivery.
    Could you tell me how to handle this situation & what item category to use which will allow me to create
    Outbound delivery so that I can proceed to post goods issue & create 0 dollar invoice?
    Thanks for your help.
    Regards,
    Pri

    Check the item category configuration for TAS. It does not have the tick for 'Item relevance for delivery'.
    This can be seen in the following path:
    IMG > Sales and distribution > Sales > Sales documents > Sales document item > Maintain item categories.
    The idea of having a 3rd party sale (with item category TAS) is that the item is directly delivered from your vendor to customer. When you perform goods receipt of the PO, it will not ask for a storage location, since the product does not enter the plant premises.
    This is a one step method to dispatch goods directly. Hence the outbound delivery is not required once GR is done.  The next step is to enter a vendor invoice followed by customer billing document.
    If you check the accounting part of the GR material document it will be
    Cost of goods sold DR
    GR/IR clearing account CR
    However, in your case, since the material is a FOC, there should not be an accounting document, and hence no vendor invoice verification / customer billing.
    In standard, the item category TAS is relevant for billing. Hence if you do not require billing (being FOC), I suggest you use another item category (a copy of TAS) without billing relevance. I guess everything else should fall in place.
    Regards,
    Aroop

  • Automatic Batch determination while creating outbound delivery

    Hi,
    I have already performed following steps, but still i am facing problem for Automatic Batch determination while creating outbound delivery :
    1.CT01- Creation of Characteristics. ( Define Selection Class )
    2.CL01- change. ( Define Selection Class )
    Add Characteristics in u2018CHARu2019 tab And save .
    3.CU70 u2013 create u2018Sorting Sequenceu2019 and assign characteristics
    4.Batch Search Procedure & Strategy type
    V/C3 u2013 Batch Search Procedure and assign the strategy types
    a.To create condition type T. code V/C1
    b.To create access sequance T. code V/C2
    5.V/C5 - Allocate SD Search Procedure/Activate Check u2013 assign sales organization , order type into Batch search procedure.
    6.V/CL - Activate Automatic Batch Determination in SD - Activate automatic batch det. for delivery item categories u2013 select item category and activate auto batch determination
    7. VCH1 u2013 Create batch search strategy against strategy type as per the access sequence needed.
    Please let me know is there any other step, apart from it.
    Tx
    Uts

    Dear saravanan,
    Re :Check from ur material master view ' Sales: General/Plant Data' that availability check should be 02 and batch management should get activated .
    Done!
    Re: check CT01 - addnl data table name and field name maintained ( which field to be taken for batch determination )
    Done!
    Re:check CL01 - char - is maintained with CT01 char
    Done!
    Re: check from v/c1 'Sort sequence' and Qty proposal 1 are maintained correctly.
    Done!
    Still i am not able to get batch automatically...
    Is there any LIFO or FIFO settings i have to maintain in Material master.
    Pl guide.
    Tx
    Uts

  • Create Inbound Delivery from Outbound Delivery create

    Hi,
    This is what I am trying to do...
    1. Create PO (me21n)
    2. Create Outbound Delivery based on PO (VL10g)
    3. PGI (this creates a DELVRY03 IDoc)
    (IDoc is created at this step, no issues so far)
    4. Based on the Outbound DELVRY03 IDoc I want to create Inbound Delivery. Inbound IDoc is created, but not posted to Application. It gives me the following error...
    "Item 00000 of purchasing document does not exist".
    Please help me resolve this error message.
    Regards,
    Sneha

    Hello Sneha,
    Outbound delivery cannot be created against the purchase order. In a third party scenario where in we receive the shipping Notification(SN) from the vendor, it comes as Delvry02 IDOC to our system. The IDOC gets posted as Inbound delivery for which Goods Recipt happens against the Purchase order using the transaction MIGO. This updates the vendor confirmation table EKES. If you see the Confirmations tab in purchase order you will see the Inbound delivery number and external delivery number.
    Outbound delivery gets created against the sales order and uses the stock posted by the goods receipt to issue the goods. The ASN signals(DelVRY03) gets created after PGI happens in the Outbound delivery.
    The Process is like
    Purchase Order(ORDERS05) goes to vendor --- > Vendor Manufactures the goods sends back Ship notifcation(SN) -> SN posts the goods Inbound Delvery is created and GR happens.-> Outbound delivery gets created and ASN signals go to the forwarder.
    Do revert to me for any further clarification.

  • BAPI for creating Return delivery to vendor using transaction MIGO

    Hi All,
             My requirement is to create Return delivery to vendor using transaction MIGO.
    In MIGO transaction to create return delivery, the following steps needs to be followed.
    i) Select the option A02 Return delivery, R02 Material document,
        Enter Material document xxxxxxxx.
        Reson for movement:xxxx
        By selecting the option item ok and via delivery check box, then save.
    After saving return delivery needs to be created.
    Is there any BAPI/FM exist for this requirement?
    I made lot of search in sdn, but i could not find any thing helpful.
    Appreciate quick help.
    regards
    surya

    Hi
    In VL02n->Extras->Delivery Output->Header
    Check if you see any message type (LD00 ?).
    If you do not see any, insert a message type LD00.
    If you want to check the IMG settings, see Txns : V/71 (for delivery types RL/RLL) and V/73 (for Item category RLLN)
    Best regards
    Ramki

  • STEPS for creating IDOC .

    I need to creat IDOC for whenever  delivery is created .

    Hi
    Take the correct Idoc type and Message Type and process code from EDBAS and EDMSG tables and use
    see the doc
    Data Creation in Idoc
    IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
    asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
    While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
    IDoc is a intermediate document to exchange data between two SAP Systems.
    *IDocs are structured ASCII files (or a virtual equivalent).
    *Electronic Interchange Document
    *They are the file format used by SAP R/3 to exchange data with foreign systems.
    *Data Is transmitted in ASCII format, i.e. human readable form
    *IDocs exchange messages
    *IDocs are used like classical interface files
    IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    FOr testing you can use WE19.
    How to create idoc?
    *WE30 - you can create a IDOC type
    For more information in details on the same along with the examples can be viewed on:
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
    http://www.sappoint.com/presentation.html
    http://www.allsaplinks.com/idoc_search.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://www.erpgenie.com/sapedi/idoc_abap.htm
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30 )
    Create Message Type ( WE81 )
    Assign Idoc Type to Message Type ( WE82 )
    Creating a Segment
    Go to transaction code WE31
    Enter the name for your segment type and click on the Create icon
    Type the short text
    Enter the variable names and data elements
    Save it and go back
    Go to Edit -> Set Release
    Follow steps to create more number of segments
    Create IDOC Type
    Go to transaction code WE30
    Enter the Object Name, select Basic type and click Create icon
    Select the create new option and enter a description for your basic IDOC type and press enter
    Select the IDOC Name and click Create icon
    The system prompts us to enter a segment type and its attributes
    Choose the appropriate values and press Enter
    The system transfers the name of the segment type to the IDOC editor.
    Follow these steps to add more number of segments to Parent or as Parent-child relation
    Save it and go back
    Go to Edit -> Set release
    Create Message Type
    Go to transaction code WE81
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter
    Click New Entries to create new Message Type
    Fill details
    Save it and go back
    Assign Message Type to IDoc Type
    Go to transaction code WE82
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.
    Click New Entries to create new Message Type.
    Fill details
    Save it and go back
    Check these out..
    Re: How to create IDOC
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    ALE/ IDOC
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    go trough these links.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
    1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
    2.IDOCs are independent of the sending and receiving systems.
    3.IDOCs are independent of the direction of data exchange.
    The two available process for IDOCs are
    Outbound Process
    Inbound Process
    AND There are basically two types of IDOCs.
    Basic IDOCs
    Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
    Extended IDOCs
    Extending the functionality by adding more segments to existing Basic IDOCs.
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30)
    Create Message Type ( WE81)
    Assign Idoc Type to Message Type ( WE82)
    imp links
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    www.sappoint.com
    --here u can find the ppts and basic seetings for ALE
    http://sappoint.com/presentation.html
    www.sapgenie.com
    http://www.sapgenie.com/ale/index.htm
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    Try this..Hope this will help.
    >>>> SAP ALE & IDOC<<<<
    Steps to configuration(Basis) >>
    1. Create Logical System (LS) for each applicable ALE-enabled client
    2. Link client to Logical System on the respective servers
    3. Create background user, to be used by ALE(with authorizaton for ALE postings)
    4. Create RFC Destinations(SM59)
    5. Ports in Idoc processing(WE21)
    6. Generate partner profiles for sending system
    The functional configuration(Tcode: SALE)
    • Create a Customer Distribution Model (CDM);
    • Add appropriate message types and filters to the CDM;
    • Generate outbound partner profiles;
    • Distribute the CDM to the receiving systems; and
    • Generate inbound partner profiles on each of the clients.
    Steps to customize a new IDoc >>>
    1. Define IDoc Segment (WE31)
    2. Convert Segments into an IDoc type (WE30)
    3. Create a Message Type (WE81)
    4. Create valid Combination of Message & IDoc type(WE82)
    5. Define Processing Code(WE41 for OUT / WE42 for IN)
    6. Define Partner Profile(WE20)
    Important Transaction Codes:
    SALE - IMG ALE Configuration root
    WE20 - Manually maintain partner profiles
    BD64 - Maintain customer distribution model
    BD71 - Distribute customer distribution model
    SM59 - Create RFC Destinations
    BDM5 - Consistency check (Transaction scenarios)
    BD82 - Generate Partner Profiles
    BD61 - Activate Change Pointers - Globally
    BD50 - Activate Change Pointer for Msg Type
    BD52 - Activate change pointer per change.doc object
    BD59 - Allocation object type -> IDOC type
    BD56 - Maintain IDOC Segment Filters
    BD53 - Reduction of Message Types
    BD21 - Select Change Pointer
    BD87 - Status Monitor for ALE Messages
    BDM5 - Consistency check (Transaction scenarios)
    BD62 - Define rules
    BD79 - Maintain rules
    BD55 - Defining settings for IDoc conversion
    WEDI - ALE IDoc Administration
    WE21 - Ports in Idoc processing
    WE60 - IDoc documentation
    SARA - IDoc archiving (Object type IDOC)
    WE47 - IDoc status maintenance
    WE07 - IDoc statistics
    BALE - ALE Distribution Administration
    WE05 - IDoc overview
    BD87 - Inbound IDoc reprocessing
    BD88 - Outbound IDoc reprocessing
    BDM2 - IDoc Trace
    BDM7 - IDoc Audit Analysis
    BD21 - Create IDocs from change pointers
    SM58 - Schedule RFC Failures
    Basic config for Distributed data:
    BD64: Maintain a Distributed Model
    BD82: Generate Partner Profile
    BD64: Distribute the distribution Model
    Programs
    RBDMIDOC – Creating IDoc Type from Change Pointers
    RSEOUT00 – Process all selected IDocs (EDI)
    RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
    RSARFCEX - Execute Calls Not Yet Executed
    RBDMOIND - Status Conversion with Successful tRFC Execution
    RBDMANIN - Start error handling for non-posted IDocs
    RBDSTATE - Send Audit Confirmations
    FOr testing you can use WE19.
    <b>Reward points for useful Answers</b>
    Regards
    Anji

  • Create a delivery note after an advance invoice is paid

    Suppose that the use of an advance invoice is that you deliver items to your client only after your client has paid the price for these items in advance.
    Now assume the following situation:
    1.
    You book an advance invoice.
    2.
    You wait until the amount of this advance invoice is paid by your client, i.e. until you are informed by your bank on the receipt of a payment.
    3.
    You book the receipt of payment in SAP.
    4.
    After this the status of the advance invoice is set to closed by SAP.
    5.
    This document status makes it unpossible to create a delivery note related to the advance invoice - the only way is to create a seperate delivery note without any relation to the original advance invoice.
    My question: Did I get the situation right? In this case I would say that the behaviour of SAP is erroneous - or are there any implicite reasons for this design decision?
    Any idea to come along with this?
    Thanks for your help!
    Frank.

    My question was too hasty.
    As I wrote in step 4 of my initial message after booking of payment in SAP the advance invoice is closed - this is correct.
    But my conclusion in step 5 is not correct in total:
    It is correct that you cannot create a delivery note as a sequel document to the advance invoice using "copy to" in the advance invoice form, since the advance invoice is already closed -
    but you can create a sequel delivery note document using "copy from" in a delivery note form related to the already closed advance invoice!
    Hence my question is obsolete!

  • Create STO,Delivery and PGI delivery from an interface

    Hi,
    We are using a third party WMS system to manifest and ship orders froma  distribution center to a store. The only data that is going to come into SAP is the Bill of Lading as to how much has shipped for a material to the store from the DC. This has to drive a Stock transport order cycle of creating an STO, create and PGI delivery. As we are building the interface,  I am a bit confused as to how we can make all this happen from one data feed.  Since there is only one feed and it has to trigger mutliple processes should we trigger multiple idocs (different types) to trigger the STO creation, create the delivery and PGI it (Delivery 03 idoc)?
    Will it be too cumbersome to build all this logic in the interface?
    Another option would be to create the STO using the feed, then run VL10B in a given time interval (Background) to create the delivery.
    However, I am not 100% sure how you can spawn off a PGI job? Even if I were to run the VL02n program in the background how can I populate the pick quantity?
    Any insight would be very useful.
    Thanks..

    My assumption is just you need to adopt delivery qty as pick qty.You are not doing any TR ,TO as your ware house is third party managed.
    you need to define the picking form EKOO to your shipping point type and then the quontity will copy
    You can do it in the difintion of the shipping point, you have to difine send time = 4
    I will explain how need to  set up this automatic picking, and then you can
    work backwards from there. The automatic picking you are experiencing
    is actually related to the output type EK00 assigned to your shipping
    point.
    Consider the following two setup steps which will result is automatic
    picking:
    Set the output type to EKOO, in the print picking list of the shipping
    point in customizing.
    Make sure the parameters below are set:
    Message Language
    Number of Messages
    Send Time <<<<<<<<<<< this must be set to 4 (send immed)!!
    Transmission Medium
    1) you have to set the parameters for EK00 in the shipping-point-
    maintenance in customizing:
    -> Enterprise Structure
    -> Definition
    -> Logistics Execution
    -> Define, copy, delete, check shipping point
    2) as second step you define the shipping-print-parameters in
    customizing:
    -> Logistics Execution
    -> Shipping
    -> Basic Shipping Functions
    -> Output Control
    -> Define print parameters shipping
    -> Shipping (Spec.case)
    Therein there should be an entry for every shipping-point, where
    you like to use the picking-list EK00!
    If you have 1 & 2 setup for a particular shipping point you will
    experience the "automatic" picking of deliveries.
    and finally picking storage  location determined as per storage conditions maintained in material master.

  • What is Cycle or steps to create Stock transfer between plants.

    What is Cycle or steps to create Stock transfer between plants.
    Reply with T Codes & Justify

    Hello RM
    We can transfer stocks within a company code between 2 plants using 3 methods:
    1) Using single step simple stock transfer (Mvt Type 301).
    2) Using two step stock transfer (Mvt Types 303 and then 305).
    3) Using a stock transport order(STO) again it is based on 2 things:
    a) r u using STO with delivery or
    b) without delivery.
    Though the first two steps are very simple to process but using STO has its own advantages: 1) Quantity in transit can be monitored 2) delivery costs can be entered in the STO.
    First 2 steps (single step and 2 step plant to plant transfer) can be done using MIGO tcode , selecting stock transfer and entering the relevant mvt types.
    would like to tell you about STO as it is an important process.
    STO without delivery, the following functions are provided to support the Internal Stock Transfer without Delivery :
    #Create Stock Transport Order
    #Post goods issue for stock transport order
    #Post goods receipt for stock transport order
    Config Step required before processing above steps:
    Setting Up Stock Transport Order: Purchasing Document Type, the purpose of this activity is to specify which document type is to be used for a certain combination of supplying (issuing) plant and receiving plant.
    Path go to SPRO--MM-Purchasing---PO-Set up STO-----assign doc type, one step procedure, underdelivery tolerances.
    There you have to enter your supplying and receving plant with the Purchasing doc type( UB).
    Now the process:
    1) Receiving plant will create a STO towards issuing plant.
    2) Issuing plant will transfer material from their unrestricted use stock to stokc in transit using mvt type 351.
    3) Receiving plant receives the goods using MIGO mvt type 101.
    Regards
    Yogesh

Maybe you are looking for