IDocs for Invioce and Delivery

Hi all,
I have to send the customer the Invoice and Delivery confirmation for that order placed by him through an IDoc in background job.
We are going for a standard IDoc for invoice and Delivery also but how to fill the data into that standard IDoc.
1.Do we have standard report like (BD12, BD14, BD10 etc.)
2.Should we develop a report to fill the data into that Idoc.
Please help me to find standard report or please help me to write code for that standard IDoc.
Thank you all in advance,
Regards,
Shalem.

Hi Shalem,
You need to do the following activities.
- Setup condition record (t/code <b>NACE</b>) for shipping (V2) and billing (V3).
- Setup output type (t/code <b>NACT</b>) for shipping (V2) and billing (V3) with transmission medium <b>A</b> (ALE).
- Setup procedures (t/code <b>NACZ</b>) for shipping (V2) and billing (V3) if required.
- Once the above setup are done, for any creation of billing and shipping will create entries into table <b>NAST</b> (Message Status).
- Then you can create IDoc using this standard program <b>RSNAST00</b>. Please ensure your ALE and IDoc configuration have been done such as BD64, WE20, WE21 and etc.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

Similar Messages

  • "Material is not the same for confirmation and delivery"

    Hello
    If this is not the right forum, my apologies. Direct me to the correct one if it is not ....
    Have been doing automated test development (HP's QTP) against SAP systems for over a year. I am not an application expert - very much a newbie when it comes to application knowledge but trying to gain some. I have "googled" the phase "Material is not the same for confirmation and delivery" and have not been able to find any references. What does this mean?
    I see this message for an iDoc using WE02. Have looked and looked but don't really know what I'm looking for.
    Clues?
    Thanks,
    DW

    DW,
    I have never seen that exact message, but I have seen similar ones.  Generically, the message probably means that you are attempting to perform a transaction against a document (perhaps a Purchase order?) and the Material number (Part Number) contained in the transaction is not the same as the Material number in the originating document in SAP.
    An example might be you have previously created a confirmation against a Purchase order, which now exists in SAP.  This Confirmation is for a specific Purchase order, item, and material.  Now, when you attempt to create an inbound delivery for the Confirmation, the material number contained in the new IDOC is different from the material number that was contained in the original Confirmation.
    I don't know what IDOC Message type you are having the problem with, but generically you can do some troubleshooting. Find the SAP Material number in the IDOC (MATNR probably).  Find the appropriate reference document number in the IDOC (confirmation number?  Purchase order number? or...?), and then manually review the document in SAP to ensure that the Material numbers are the same.
    If you are totally lost, you should really consult with an SAP App expert.  I am guessing that this is part of the Materials Management module, so you would be asking for an MM expert.
    Or, you can send more details, and we can try to help.
    What is the IDOC message type?
    What is the Message number of the error message?  Functionally, what is this IDOC trying to do, from a business perspective?
    Rgds,
    DB49

  • Problem with IDoc for an outbound delivery

    Dear All,
    I am facing a problem with the IDoc defined for an outbound delivery.
    Scenario:
    Implementation of a small enhancement for an IDoc (DESADV, DELVRY01) created for an outbound delivery (in VL02N).
    What I did:
    I implemented the EXIT_SAPLV56K_002 exit in the V56K0001 enhancement, activated in SMOD, assigned V56K0001 component in CMOD and acivated it. Then I put a breakpoint on the ZXTRKU02 include. For me everything in SMOD and CMOD looks OK.
    I have also created a partner profile, port, outbound message config. (message DESADV, basic type DELVRY01, application V2, output message type LAVA, process code DELV. function module used for this process code is IDOC_OUTPUT_DELVRY).
    What I can do:
    I can issue an IDoc message, it looks ok and contains the standard data.
    Problem:
    It seems that the enhancement does not work. Finally I put there only one line of code to avoid a program bug and just to check . The system does not stop at the breakpoint (set on the ZXTRKU02 include in the EXIT_SAPLV56K_002 exit).
    Am I using the proper exit? I appreciate any suggestions.
    Thanks,
    Grzegorz Skorus

    Hello Grzegorz
    Not an expert on this, but noone is responding so I thought let me try and help you. You seem to be doing the right things as mentioned in OSS note 1498409.
    Firstly since this can be called form Shipment Idoc also, you may need to make a differentiation by the interface parameter 'MESSAGE_TYPE' or segment name. See the attached OSS note, though it belongs to older releases,  it may help you.
    Also help says 'The callup of this function module is programmed for each enhancement of the internal table for the IDoc (in other words, when you add an extra segment'. So may be you need to add an extra segment/field to make it work.
    Futher  the user exits are replaced by BADIs. May be you should use exit_badi_v56k.
    Hope this helps and others will pitch in.
    1498409 - Valuation Type unavailable when creating deliveries using IDOC
    631913 - Exit after formatting delivery IDoc type DELVRY

  • IDOC for sheduling agreement delivery schedules (without Forecast/JIT)

    There is an outbound IDOC DELINS to trasmit MM scheduling agreement (Doc.type LPA) delivery schedules of type Forecast/JIT using release procedure. But, can I create outbound IDOC DELINS to transmit MM scheduling agreement (Doc.type LP without release procedure) schedule lines (without specifying forecast/JIT shcedule lines)? When this IDOC is transmitted and processed as an inbound IDOC, it should add schedule lines to a Schedule agreement (Doc.type DS) in SD module. Thanks. Satya.

    Hi Anil ,
    Goto Transaction NACE , Select Application EL and then Click on O/p Types.
    Select your o/p and click on Processing routines.
    Make a copy of medium 1 and change it to 5. The program , Form , Form routine would remain the same.
    Maintain condition records with medium 5 in MN10.
    Ensure that email address exists in Vendor Master.
    Check with ur Basis to make sure that the setting are done in Transaction SCOT for sending document via PDF.
    Create a new Agreement and test it.
    Regards
    Ramesh Ch

  • Idoc for materials and service for same contract.

    Dear All
       I have an scope where i have to migrate the data for material and services for the same contract.Is there an Idoc which does it so or otherwise ?Earlier in scope materials contracts have been loaded with the help of idoc type :- PURCONTRACT_CREATE01  and that of Service Contract using Idoc type :- BLAORD03.No customization is however permitted .Tcode for the same is ME32K.
    Regards
    Somnath

    Hi,
    It is not clear to me if you are working with sapscript or smartforms.
    You have only to find a variable which identifies the kind of invoice
    I do not know that variable so i use an example variable
    for sapscript:
    /: IF &VBDKR-FKTYP& = '1'
    /  INVOICE
    /: ELSE
    /  SERVICE ORDER
    /: ENDIF.
    In a smartform you can also do something like that.
    but There you work with conditions (eq, BOOLEAN)
    You have only to find the right variable
    success,
    Gr., Frank

  • Invoice Posting using INVOIC02 Idoc for PO and Non-Po based invoices

    Hi All,
      We have a problem regarding posting Invoices using Idocs.
    We have po and non-po invoices coming frm thirdparty in the form of idoc files.
    We need a clarification whether Invoic02 idoc can handle both Po and Non Po Based invoices or threre are seperate idoc types or message types for Po and Non Po Invoices.
    Could any one give some inputs on Partner Profiles also for this senario.
    Please kindly reply as early as possible.
    Regards
    Anil Kumar K

    Hi
      I Got your name from this site.I would be very thankful if you can help me here.I am designing a EDI based invoice LIV.Is it possible to post some charges which are without PO reference but are coming in Vendor Invoices.Is it possible to post these kind of charges with EDI message INOIC01 or we have to post through FI posting.If possible through EDI in which segment of IDOC we will enter these charges with amt.Also is it possible to post credit memo also with EDI
    Thanks
    Sanjeev

  • IDocs for Notification and Work Order messages to third party software

    Dear all,
    Our client have a third party software in which he intends to manage the Notifications for PM. Now he wants that, when the Notification is created into SAP, the Notification number from SAP to be sent to the third-party software. Also, from the WO created from the Notification, to the third party software have to be sent the WO number and the status of the WO and, each time the status of the WO is changed, the new status have to be sent to the third party software, until the status of the WO is TECO.
    Please, can you help me, I am totally uninitiated of the IDocs and I don't know if there are some standard IDocs that can be used for this and how to manage them.
    Thank you very much for your help.
    Kind regards,
    Sorin

    Hi Sorin, 
    There are idoc types INOTIF and IORDER available but please refer to SAP note 812542 which states that the recommended way of transferring the data to third party software is to make use of the available BAPIs. Please note, the mentioned idocs will not benefit from future developments, but they
    will still be  supported in their current state. 
    However, please refer to the existing PM BAPIs in transaction BAPI. Specifically BAPI_ALM_ORDER_GET_DETAIL and BAPI_ALM_NOTIF_GET_DETAIL can be used to read
    data from the order and notifications. This data can then be exported in a way that suits your requirements.
    I hope this helps,
    Siobhan

  • DEBMAS IDOC for CREATE and UPDATE

    How do i use DEBMAS IDOC dynamically for create and update customer information.
    I have a file as source which would have combination of information for new and change customer information. and there is a field in the file with t code xd01(create) and xd02(update).
    Please advise.
    -Vasu

    Hi,
    The field MSGFN is the one which decide the operation.
    Please pass the values accordingly to indicate the Create/Update.
    In inbound IDOC case ,process code will check MSGFN and do the action.
    Regards,
    Akshay.

  • RFC For Order and Delivery creation in SD from CRM - text not getting copie

    Hi
    I am trying to find out how the order and delivery is created in R3 if I create a return order in CRM, as we have one issue in which the text is not being copied to delivery??
    Thanks in advance
    Sameer

    Please check if you have any custom code/user exit in ECC which uses transaction code (VA01 , VA02 or VA05 etc) prior to invoking credit checks. 
    Orders created via CRM will not have transaction code set (SY-TCODE).

  • Outbound idoc for MIGO and MB1B

    Hi,
    MBGMCR03 is also not working. Any other idoc to trigger to o/b idoc for both MIGO & MB1B.
    Thanks & Regards,
    Balaji

    hi,
    This idoc WMMBID02, i'm using for inbound. The same i tried for outbound also.
    In WE20, in outbound parameters, for LS partner, for Message type WMMBXY, i've maintained the receiver port & basic type as WMMBID02.
    In BD64, i've created a model view for this message type & distributed the same.
    Then i've tried both MIGO & MB1B, this idoc not triggered at all.
    Any other settings other than this...
    Thanks & Regards,
    Balaji

  • Letter of credit  maintenance for order and delivery documents

    Hi Friends,
    As there are three places where we can maintain Letter of Credit ( Financial documents) data.as
    1. Order Header data
    2. Order Item data
    3. Delivery Header data
    What is the importance of all these and ideally where shd maintain ?
    kindly guide
    Shailesh

    Hi,
    Process Of Letter of Credit for Imports
    1. The Clearing agent ask for amount, the person who receive the product will give Letter of Authority to Clearing Agent. The clearing agent move to bank and take check.
    For this purpose, we just issue LA.
    2. Prepare Purchase for the Vendor from whom we are going to receive the product. There may be 2 or more Vendors.
    1. Product cost to be transferred to Vendor A
    2. Freight or Other Charges to Vendor B
    3. Customs Duty and Others to Vendor C
    Tcode : Me21n
    3. First We have to pay Customs Duty to Commissioner of Customs after LA issued.
    Entry : Customs Clearing a/c Dr
    Cess on Custom a/c Dr
    CVD Clearing a/c Dr
    Cess on CVD a/c Dr
    Special CVD a/c Dr
    Vendor C a/c Cr.
    T-code :MIRO or YMIROOTH
    4. Cenvat credit for the product will be taken by person who handling Excise in that company
    Entry : Cenvat Clearing a/c Cr.
    RG23A Part II a/c Dr.
    5. Clearing of Cenvat Credit
    Entry : Cenvat Clearing a/c Dr.
    CVD clearing a/c Cr.
    Cess on CVD a/c Cr.
    Special CVD a/c Cr.
    6. After Bank payment they will transfter to us
    Entry : Vendor a/c - Dr.
    Bank a/c - Cr.
    Give ur mail id.. i will send the doc. its not easy to make u understand that concept.
    Regards
    Srikanthraj

  • Route determination for PO and Delivery

    Hi Experts,
    I would like to ask how to set up route fro deliveries and Stock transport orders.
    Hope you can help me on this.
    Thank you very much.
    Regards,
    Mylene

    Working with Route Schedules
    Use
    Using a route schedule, you can control periodic customer deliveries of a particular shipping point to different ship-to parties (for example, customers or stores) in a certain sequence on a certain defined route. The planning is based on calendar weeks. The period unit is a day. Also, route schedules have a goods issue time.
    The route schedule function supports the following processes:
    Periodic deliveries from a shipping point to stores or customers are planned in advance on the basis of calendar weeks and weekdays, also without reference to particular deliveries.
    You adapt the schedules in the specific cases to the planning. For example, you can plan a GI date for a Monday at 8 o’clock, without knowing the exact date or the delivery.
    On the basis of this planning, deliveries that are to leave the warehouse at the same time are combined into groups. In Shipping you can thus distribute the workload by processing these groups.
    Features
    You can display all deliveries for a particular route schedule on a particular day, for a particular shipping point, and so on. In this way, for example, you can choose picking lists on the basis of route schedules.
    You can create route schedules for the following documents:
    Sales orders
    Stock transfer orders
    Deliveries that are based on sales orders, store orders, stock allocations, stock transfer orders, and deliveries without reference.
    The route schedule is displayed in the header data of the delivery. For each delivery within the route, the system prints the expected date and the expected time of the delivery (on the basis of the local time at the original shipping point) on the delivery note; the goods issue date is used for the goods issue posting and the stock valuation.
    In Customizing, you define for each shipping point, delivery type, stock transfer order, and order type whether or not route schedules are to be used.
    You create the route schedules in the master data for shipping. Here you define the route schedule determination and the validity period for the route schedule and the itinerary.
    As soon as the legs have been defined, you can branch to another screen to determine the actual itinerary, as well as the time (days/hours/minutes) required to get from one unloading point to the next. In this screen there is a field beside each leg. Here you can enter the number of the itinerary for the individual legs of the route. If, for example, you enter legs A and B, but assign itinerary number 2 and 1 to these, B is the first unloading point on this route. If you press Enter, the legs are displayed in the correct sequence.
    At the same time it is possible to control the route schedule determination for each delivery type, stock transfer order, and order type. It is activated in the same manner as the repeated route determination. If the route schedule determination for a delivery is active, the system automatically attempts, during creation or change of a delivery, to determine a route schedule and records this in the delivery. Simultaneously, the scheduling is adjusted. All the deadlines, for example, the transportation planning time, the picking time, the loading time, the goods issue time, and the delivery time can change.
    Deliveries with the same route schedule and the same date can be selected for the same picking run and the same goods issue. The same procedure can be used for printing delivery notes and freight lists, for the grouping of deliveries into shipments, and for confirmation of picking orders.
    Deliveries that leave the warehouse at the same time, but are assigned to different routes and can therefore have different route schedules, can be combined together and processed through the creation of wave picks. The only condition is that all deliveries have the same goods issue time.
    Route Schedule Determination
    If exactly one route schedule is defined for a particular combination of requirements, then the system will use this.
    For each combination of requirements for the route schedule determination, you can define several route schedules.
    In the case of a delivery without a preceding document, the system determines the route schedule with the earliest delivery time at the ship-to party.
    In the case of deliveries based on preceding documents (for example, stock transfer orders), the system searches for the route schedule that is nearest to the planned date/time of the delivery. The system uses the following search algorithm:
    - If a route schedule exists for the specified time, this is assigned to the delivery.
    - If there is no route schedule for the time specified, the system searches for the previous route schedule up to the GI time.
    - If there is no route schedule from the GI time to the planned time, the system searches for the next route schedule in the future and assigns this to the delivery.
    Requirements for Route Schedules
    The route schedules are determined by the following conditions:
    · Shipping point
    Where are the goods coming from?
    Ship-to party and unloading point
    Where are the goods going to?
    Shipping condition
    How are the goods being shipped?
    Transportation group
    Which goods are shipped?
    ® For example, which type of goods?
    Calendar week / year
    When are the goods to be shipped?
    If you do not explicitly enter the week and the year, the entry applies for each calendar week. If you enter a week and a year, the route schedule only applies for this week.
    You can only use route schedules if you have maintained the working times and therefore at least one of the following times in minutes:
    · Transportation planning time
    · Pick/pack time
    · Loading time
    · Transit time
    A route schedule can leave the warehouse exactly once in a week. If a route schedule runs several times, either on several days or several times a day, it must be copied to another route schedule.
    Special schedules and public holiday weeks are possible.
    Processing a Route Schedule
    Implementation Options
    Wholesale trade customers and stores can receive goods at regular intervals. These delivery rhythms have an influence on the workload in the warehouse. To help delivery planning, the route schedule serves as a tool for planning regular, repetitive customer deliveries on a particular route. At the time of planning, potential deliveries that have not yet been created are grouped in the route schedule. When the deliveries are created, the system can automatically determine a route schedule and assign it to the delivery. All deliveries with the same route schedule and the same date can be processed together in the shipping point. All these deliveries leave the shipping point together at a particular time. They are distributed along the same geographical route.
    · Deliveries for route schedule MO10H leave the shipping on Mondays at 10:00 in the direction of Philadelphia.
    · Deliveries for route schedule MO10M leave the shipping point on Mondays at 10:00 in the direction of Boston.
    · Deliveries for route schedule MO10S leave the shipping point on Mondays at 10:00 in the direction of New York.
    You can print picking lists for all deliveries that belong to route schedules MO10H - MO10S together.
    Prerequisites
    If you want to define route schedules, you must perform the following tasks:
    - Activate the route determination
    - Activate the delivery scheduling
    - Activate the route schedule for your shipping point and make the following settings:
    Transaction
    Activity
    Delivery
    Route schedule determination for delivery type
    Sales order
    Route schedule determination for sales document type
    Stock transfer order
    Route schedule determination for delivery type
    Set delivering plant and order type
    Maintenance of the itinerary should be uniform for all the route schedules used. To ensure exact planning, maintain the itinerary for all the route schedules. If rough planning is sufficient in this case, you do not need to maintain the itinerary for a route schedule.
    If you do not define any goods accepted times in the customer master for the unloading points of the ship-to party, the system assumes that the goods acceptance is possible at any time. The system determines the delivery time from the departure time in the route schedule plus the required traveling time to the ship-to party, as set in the itinerary (specific move time). This delivery time must be within the goods acceptance time of the unloading point of the ship-to party. If not, the respective route schedule is not determined during delivery creation.
    For more information on route schedules, refer to the Implementation Guide (IMG) under Route Schedules.
    Process Flow
    Select the shipping point you are working for and enter the number of the route schedule.
    Enter the data that defines the route schedule more exactly:
    - Description of the route schedule
    - Route
    - Departure day (weekday)
    - Departure time
    You define the route schedule determination. When you create the delivery, the system can determine a route schedule on the basis of the following data:
    - Shipping point
    - Ship-to party
    - Unloading point (if available)
    - Shipping condition
    - Transportation group
    - (Optional) year/period
    You enter this data (with the exception of the shipping point already entered in step 1).
    You decide whether or not you wish to define the itinerary for this route schedule.
    (Optional) You enter the itinerary and, if required, also the travelling time.
    Creating a Route Schedule
    Choose Logistics ® Logistics Execution ® Master data ® Transportation ® Routes ® Route schedule ® Create.
    In the screen Create Route Schedule: Initial Screen, enter the shipping point and the number of the route schedule.
    If you wish to use data from an existing route schedule as a reference, enter the respective shipping point and the number of that route schedule. If you also wish to copy the itinerary, check the Copy itinerary box.
    Press ENTER .
    The Create Route Schedule screen appears (here the system displays the number you just entered for the route schedule and the shipping point).
    Enter the following data:
    Description of the route schedule
    The respective route
    Departure day (weekday)
    Departure time
    In the Determine route schedule section, enter the following data:
    Ship-to party
    Unloading point (if available)
    Shipping conditions
    Transportation group
    (Optional) Year/period
    If you wish to define for this route schedule the itinerary according to which the individual ship-to parties are to be delivered to, choose Extras ® Itinerary.
    The Create Itinerary screen appears.
    Enter the itinerary and, if necessary, the travelling time.
    When you determine the travelling time from one ship-to party to the next, you should include the wait time of the vehicle at the previous ship-to party.
    If the same route is planned for several route schedules, define for each of these route schedules the same itinerary that should correspond to the stages and legs of the route.
    Choose Goto ® Back.
    You return to the Create Route Schedule screen.
    In this screen, the Itinerary maintained field is now selected. If you wish to add other ship-to parties, you must also maintain the Itinerary for them.
    Check your data and save your entries.
    Reward if helpful...
    Regards,
    Diogo

  • Common Table required for Shipment and Delivery

    Hi Guys,
                 What is the Table where I can give input as Shipment Number and get all the deliveries for that Shipment.
    Thanks,
    Prasad.

    HI
    YOU CAN GET IT FROM TABLE VTTP   by giving input as shipment no. u will get  delivery no. from this table and then from table LIPS by using this delivey no. u can get all delivery details.
    and in addition to that u can also refer link: https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e944e133-0b01-0010-caa2-be2cb240f657
    regards
    rahul
    Edited by: RAHUL SHARMA on Feb 20, 2009 8:11 AM

  • IDOC for roles and profiles

    Hi Guru.
    I need this: I wish to export the new and the modified roles and profiles to an external non-SAP system. This non-SAP system is able to receive iDoc message.
    Is it possible? Can I find n the SAP system the change point and the iDoc to do this?
    Regards
    Manuel Chiarelli

    not for roles. no. you can:
    transport them
    up-/download them
    RFC-copy them
    but not idoc them.

  • XMLP for EBS and delivery notifications

    Ok, I'm using XMLP in EBS to generate various reports. Nothing fancy, just some rdf's called from a concurrent program with the output set as XML and templates for each. I schedule most of the reports in the concurrent manager and set the notify upon completion to send an email with a link to the report when complete. This has worked fine for about a year.
    Recently, we have started seeing issues. The reports seem to be completing with no errors, but the email notifications are going out with no link in them. It's not report specific, as sometimes a report will complete and send the email with link just fine, and other times it sends the email with no link. It seems random and not easy to recreate.
    Unfortunately the issue may just be my lack of knowledge on how these reports are generated and delivered. After some research and testing, I have a question. What seems to be happening is that when the concurrent program completes successfully, it kicks off the output post processor to finish the report generation, but also fires off the email before that process is complete. So I guess my question is does the email notification get sent once the concurrent program is complete (regardless of whether is spawns the OPP or not), or does it get sent after the OPP completes? And, if it's the former, why wouldn't I have seen this issue long ago? And, also if it's the former, would upping the OPP Response and Process Timeout profile options help?
    Thanks

    Ok, I'm using XMLP in EBS to generate various reports. Nothing fancy, just some rdf's called from a concurrent program with the output set as XML and templates for each. I schedule most of the reports in the concurrent manager and set the notify upon completion to send an email with a link to the report when complete. This has worked fine for about a year.
    Recently, we have started seeing issues. The reports seem to be completing with no errors, but the email notifications are going out with no link in them. It's not report specific, as sometimes a report will complete and send the email with link just fine, and other times it sends the email with no link. It seems random and not easy to recreate.
    Unfortunately the issue may just be my lack of knowledge on how these reports are generated and delivered. After some research and testing, I have a question. What seems to be happening is that when the concurrent program completes successfully, it kicks off the output post processor to finish the report generation, but also fires off the email before that process is complete. So I guess my question is does the email notification get sent once the concurrent program is complete (regardless of whether is spawns the OPP or not), or does it get sent after the OPP completes? And, if it's the former, why wouldn't I have seen this issue long ago? And, also if it's the former, would upping the OPP Response and Process Timeout profile options help?
    Thanks

Maybe you are looking for