RSNASTED

HI Guys,
I am SD consultant dont have much idea on this program.
In one of the invoice we have a message type called ZSG with medium ALE sends info to other system system via IDOC, under NACE pgm attached for this is RSNASTED.
In  Idoc there is a segment E1EDK01 there is one more sug segm Z1TRANS with fiels shipment no# qty.
Problem here is in one of the Idoc created by invoice this field is filled, and when we try to create same for another plant this Z1TRANS is not filling up.
I am trying to search as normal to find the program logic with search term "VTTK" in RSNASTED program its not giving any serach results.
If iw anted to know the logic for this message type where to find ?
How to view and search RSNASTED what is the srach term to be used?
Reg
Shan1242

hi..
Note: There may not be problem in user exit since the data is filled for other plant.
The Reason why the data is populated into the Custom Segment could be bcoz of not assigning the IDOC Extension in the Partner profile for that particular Plant.
To Check this go thru these steps in the Sending system:
1. Open the Partner profiles - WE20
2. Select the Partner Number (Logical system) of the plant where data is not filled.
3. Doble click on the Outbound Message ORDERS
4. Check the Assigned  idoc types
             Basic type : ORDERS03
             Extension  : <Here u must assign the Extended Idoc type>
Let me know the result.

Similar Messages

  • SAP Report RSNASTED

    Hi all,
    I copied SAP standard report RSNASTED. Then I assigned the copy as IDOC processing program to an output type. Once I'm creating that output message I got an 'A' error because the internal table for the IDOC data (type EDIDD) is empty. After the error there is no PO on the database, there is no NAST record.
    Do I need to register the new program anywehere before it is working proper or is here in the community any other idea because the table is empty?
    Thanks for your effort in advance.
    Norbert

    Hi,
    No Need to create a output type, Go to ME22N and click on messages --> Give Output type NEU
    Here medium should be 6 I.e EDI then click on further data there you should give dispatch time 4i.e send immediately
    then that will create a entry in the NAST table
    and then you RSNAST will pick that po from NAST table
    Regards
    Krishna

  • RSNASTED - Functional Specifications

    Hi Experts,
    I would like to know if any document(s) is/are available on program RSNASTED that is used to generate EDI Invoices for Customers. I am looking for a document on how this program works, what data gets picked from where and such related information.
    If any of you can provide me that document/link, it would be helpful.
    Of course you will be rewarded for helping

    Hi,
    Check the links;
    [RSNATED|Re: WHAT IS RSNASTED?]
    [RSNAT00 AND RSNASTED|Re: RSNAST00  & RSNASTED]
    Regards,

  • RSNASTED Query

    We need to send an outbound idoc (DELVRY03) on Post Goods Issue in VL02N. All config and custom code is working fine. The idoc is generated. However, we also need to know teh idoc number as soon as the idoc is generated. This idoc number needs to be saved in a custom table. The program RSNASTED creates the idoc number. The FM, IDOC_OUTPUT_DELVRY does not hold the idoc number. So I copied the program RSNASTED to custom program ZRSNASTED and attached to the output type for medium EDI in tcode NACT (output types).
    If I execute tcode VL02n and go to Extras -> Delivery Output-> Header and select the output type (ZALU, in this case) and save the settin gs and then go do the PGI, the idoc is generated successfully.
    But if we click on the PGI button in VL02N, then no idocs are generated. When it was RSNASTED, this button successfully generated the idocs.
    Is there anything I am missing in the config or code? Any help will be appreciated.

    Resolved it myself. It seemed to be a data error rather than a coding error.

  • RSNAST00  & RSNASTED

    I am new to IDOC and I am trying to learn OUTBOUND IDOC by Message Control.
    Can somebody explain where RSNAST00 AND RSNASTED are used in the process of creating outbound idoc.
    Thanks in advance.

    Hi,
    Check this one The simplest way to create IDocs, is to write an ABAP. The individual ABAP can either be a triggering ABAP which runs at certain events, e.g. every night, or it can be an ABAP which does the complete IDoc creation from scratch.
    Triggering ABAP
    A triggering ABAP would simply try to determine which IDocs need sending and call the appropriate IDoc creation routines.
    ABAP creates the whole IDoc
    You may also imagine the ABAP to do all the job. As this is mostly reinventing the wheel, it is not really recommended and should be reserved to situation, where the other solution do not provide an appropriate mean.
    1.1 NAST Messages Based Outbound IDocs
    You can use the R/3 message concept to trigger IDocs the same way as you trigger SAPscript printing.
    One of the key tables in R/3 is the table NAST. This table records reminders written by applications. Those reminders are called messages.
    Applications write messages to NAST, which will be processed by a message handler
    Every time when an applications sees the necessity to pass information to a third party. a message is written to NAST. A message handler will eventually check the entries in the table and cause an appropriate action.
    EDI uses the same mechanism as printing
    The concept of NAST messages has originally been designed for triggering SAPscript printing. The very same mechanism is used for IDocs, where the IDoc processor replaces the print task, as an IDoc is only the paperless form of a printed document.
    Condition technique can mostly be used
    The messages are usually be created using the condition technique, a mechanism available to all major R/3 applications.
    Printing, EDI and ALE use the same trigger
    The conditions are set up the same way for any output media. So you may define a condition for printing a document and then just change the output media from printer to IDoc/EDI or ALE.
    Figure 1: Communicating with message via table NAST
    NAST messages are created by application by calling function module MESSAGING
    Creating NAST messages is a standard functionality in most of the SAP core applications. Those applications - e.g. VA01, ME21 - perform calls to the central function module MESSAGING of group V61B. The function module uses customizing entries, mainly those of the tables T681* to T685*.
    NAST contains object key, sender and receiver
    A NAST output message is stored as a single record in the table NAST. The record stores all information that is necessary to create an IDoc. This includes mainly an object key to identify the processed object and application to the message handler and the sender and receiver information.
    Programs RSNAST00 and RSNASTED provide versatile subroutines for NAST processing
    The messages are typically processed by
    FORM ENTRY in PROGRAM RSNAST00.
    If we are dealing with printing or faxing and
    FORM EDI_PROCESSING in PROGRAM RSNASTED.
    If we are dealing with IDocs
    FORM ALE_PROCESSING in PROGRAM RSNASTED.
    If we are dealing with ALE.
    The following piece of code does principally the same thing as RSNAST00 does and makes full use of all customizing settings for message handling.
    FORM einzelnachricht IN PROGRAM RSNAST00
    TABLES: NAST.
    SELECT * FROM NAST ...
    PERFORM einzelnachricht IN PROGRAM RSNAST00
    Programs are customized in table TNAPR
    The processing routine for the respective media and message is customized in the table TNAPR. This table records the name of a FORM routine, which processes the message for the chosen media and the name of an ABAP where this FORM is found.
    1.2 The RSNAST00 ABAP
    The ABAP RSNAST00 is the standard ABAP, which is used to collect unprocessed NAST message and to execute the assigned action.
    RSNAST00 is the standard batch collector for messages
    RSNAST00 can be executed as a collector batch run, that eventually looks for unprocessed IDocs. The usual way of doing that is to define a batch-run job with transaction SM37. This job has to be set for periodic processing and start a program that triggers the IDoc re-sending.
    RSNAST00 processes only messages of a certain status
    Cave! RSNAST00 will only look for IDocs which are set to NAST-VSZTP = '1' or '2' (Time of processing). VSZPT = '3' or '4' is ignored by RSNAST00.
    For batch execution a selection variant is required
    Start RSNAST00 in the foreground first and find the parameters that match your required selection criteria. Save them as a VARIANT and then define the periodic batch job using the variant.
    If RSNAST00 does not meet 100% your needs you can create an own program similar to RSNAST00. The only requirement for this program are two steps:
    Read the NAST entry to process into structure NAST
    tables nast.
    data: subrc like sy-subrc.....
    select from NAST where .......
    then call FORM einzelnachricht(rsnast00) to process the record
    PERFORM einzelnachricht(rsnast00) USING subrc.
    1.3 Sending IDocs Via RSNASTED
    Standard R/3 provides you with powerful routines, to trigger, prepare and send out IDocs in a controlled way. There are only a few rare cases, where you do not want to send IDocs the standard way.
    The ABAP RSNAST00 is the standard routine to send IDocs from entries in the message control. This program can be called directly, from a batch routine with variant or you can call the FORM einzelnachricht_screen(RSNAST00) from any other program, while having the structure NAST correctly filled with all necessary information.
    RSNAST00 determines if it is IDoc or SAPscript etc.
    If there is an entry in table NAST, RSNAST00 looks up the associated processing routine in table TNAPR. If it is to send an IDoc with standard means, this will usually be the routine RSNASTED(EDI_PROCESSING) or RSNASTED(ALE_PROCESSING) in the case of ALE distribution.
    RSNASTED processes IDocs
    RSNASTED itself determines the associated IDoc outbound function module, executes it to fill the EDIDx tables and passes the prepared IDoc to the port.
    You can call the standard processing routines from any ABAP, by executing the following call to the routine. You only have to make sure that the structure NAST is declared with the tables statement in the calling routine and that you fill at least the key part and the routine (TNAPR) information before.
    TABLES NAST.
    NAST-MANDT = SY-MANDT.
    NAST-KSCHL = 'ZEDIK'.
    NAST-KAPPL = 'V1'.
    NAST-OBJKY = '0012345678'.
    NAST-PARNR = 'D012345678'.
    PERFORM einzelnachricht_screen(RSNAST00).
    Calling einzelnachricht_screen determines how the message is processed. If you want to force the IDoc-processing you can call it directly:
    TNAPR-PROGN = ''.
    TNAPR-ROUTN = 'ENTRY'.
    PERFORM edi_processing(RSNASTED).
    1.4 Sending IDocs Via RSNAST00
    Here is the principle flow how RSNAST00 processes messages for IDocs.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b7dbd43d711d1893e0000e8323c4f/content.htm
    Regards,
    Priyanka.

  • Debug ZXM06U02 include file called from RSNAST - outbound PO IDOC

    Hi,
    I have been asked to amend an idoc to include additional fields from the Purchase Order. I have successfully extended the right idoc segments and discovered that the values I need to be added are done at include ZXM06U02. In fact I have hardcoded the 3 values here so that I can test that the hardcoded values are coming out on the Idoc.
    This is all working smoothly however I now need to do the actual work and get the values into the include. However I cant seem to get the debugger to stop at this program/include. I have tried both the standard /h with breakpoints and even WE19 (IDOC test) with debugger but I cant stop at this file to see what information I have available!
    Could someone offer me any advice on how to debug in this situation. I think it may have something to do with the RSNAST as the program in the output - although could be wrong.
    Cheers
    Paul

    Hi Paul,
    Set the dispatch time of the output type which triggers the IDoc in the Purchase Order to '3 Send with application own transaction'. The trigger the output with transaction ME9F (of course after you have put a breakpoint in the include). Now you stop at the breakpoint.
    Regards,
    John.

  • RSNASTED not showing job name

    Hi,
    I am working in SAP-AFS retail
    We have batch job scheduling.I know the output type from which i found out the program name as RSNASTED. My requirement is to find the Job names for the program RSNASTED. When i enter the program name RSNASTED in SM37 i am getting the message "No job matches the selection criteria".
    Similarly when i enter the program name in table TBTCP -->(field Rept name) still i am getting the same message.
    Why is it so.?
    All the jobs are scheduled through J5HEN Batchman.

    Because - that is not the right program. Can you try with RSNAST00?

  • WHAT IS RSNASTED?

    HI,
    what is rsnasted ? and when we will go for it..
    regards
    ganesh

    RSNASTED itself determines the associated IDoc outbound function module, executes it to fill the EDIDx tables and passes the prepared IDoc to the port.
    You can call the standard processing routines from any ABAP, by executing the following call to the routine. You only have to make sure that the structure NAST is declared with the tables statement in the calling routine and that you fill the at least the key part and the routing information before.
    TABLES NAST.
    NAST-MANDT = SY-MANDT.
    NAST-KSCHL = 'ZEDIK'.
    NAST-KAPPL = 'V1'.
    NAST-OBJKY = '0012345678'.
    NAST-PARNR = 'D012345678'.
    PERFORM einzelnachricht_screen(RSNAST00).
    Calling einzelnachricht_screen determines how the message is processed. If you want to force the IDoc-processing you can call it directly:
    TNAPR-PROGN = ''.
    TNAPR-ROUTN = 'ENTRY'.
    PERFORM edi_processing(RSNASTED).
    PLZ REWARD POINTS

  • IDoc output type not getting configured in IDoc-File scenario

    Hello
    I am having IDoc to file scenario where I want to post Delivery Document to legacy system. For this I have configured following EDI configuration for Delivery through NACE transaction
    1] Created output type
    2] Created partner function as EDI LS for this output type
    3] Configured RSNASTED as Processing Routines for output type
    4] Included this output type in the Header output procedure
    5] Configured XI system as the partner in partner profile with appropriate Message control
    Still when I attempt to include this output type in the Delivery it gives me "Output for partner could not be configured". The detail message says "In Customizing, the 'CannotBeChanged' indicator has been set for output type".
    I checked in SPRO but could not find such flag.
    Does anyone had came across such output type configuration.
    Thanks in advance.
    I know this question might be not appropriate in XI forum as it comes under EDI but it has become necessary for XI profs -:)
    Regards
    Rajeev

    Hi,
    Please check the following
    1. Condition Table
    SPRO > Material Management> Purchasing -> Message -> Output Control->Condition Tables->Define Condition Table for Purchase Order
    Select:
    Purchasing Doc. Type,
    Purch. Organization,
    Vendor
    2. Access Sequences
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Access Sequences->Define Condition Table for Purchase Order
    3. Message Type
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Types->Define Message Type for Purchase Order
    Copy NEU to ZNEU or YNEU
    4. Message Determination Schemas
    4.1. Message Determination Schemas
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Maintain Message Determination Schema
    4.2. Assign Schema to Purchase Order
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Assign Schema to Purchase Order
    5. Partner Roles per Message Type
    SPRO -> Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message Type ->Define Partner Role for Purchase Order
    6. Condition Record
    Navigation Path: SAP Menu-> Logistics -> Material Management -> Purchasing-> Master data->Messages-> Purchase Order-> MN04-> Create
    Now you create PO (ME21N) and save it. Go to ME22N and print the PO by giving output type ZNEU or YNEU.
    G.Ganesh Kumar

  • Customer not getting displayed in PDF when sales order is received in email

    Hi,
    We are using a Z smartform for printing order acknowledgement for sales order.When printing the same on paper or in print preview, the output is correctly displayed. However, when automatic pdf is received in email, customer field is missing.
    Any suggestion why this could be?
    Below are the configurations in nace transaction for this output type:
    Output Type     YA02   
    Application        V1     
    Medium               Short text                        Program                         Form Routine      Form            Smartform
    1     Print output                           /SMB40/RVADOR01     ENTRY                          Y_ORDER_ACK_NEW
    2     Fax                           RVADOR01                          ENTRY     RVORDER01
    6     EDI                           RSNASTED                          EDI_PROCESSING                    
    8     Special function     /SMB40/RVADOR01          ENTRY                          Y_ORDER_ACK_NEW
    A     Distribution (ALE)     RSNASTED                         ALE_PROCESSING                    
    TIA
    Vartika

    Hi Vartika
    Take help of ABAP developer to debug smartform. when Smartform converts data into PDF may be customer number is missing.
    Regards
    Nagendra

  • Help required on OutBound IDoc for FI Invoices

    Hi All,
    I had a requirement to create a custom idoc for FI invoices via a user exit and these idocs will be routed (via RFC) to a JAVA server/processor. Pls suggest how can i acheive this.
    Is there any user exit for acheiveing this or can we proceed further without user exit also.
    If so how to acheive this.
    Thanks & Regards,
    Anil.

    One option that immediately pops up is
    Using Output Types: like for example transaction V/40
    Application: V3 Billing
    You can define a unique output type : ZINV
    Transmission Medium : 6
    Processing Routine
    Program:         RSNASTED
    Form Routine:    EDI_PROCESSING
    You can then use WE20, and define a unique customer / and map message control (ZINV) information in outbound parameters.

  • Outbound delivery replication in target system

    Hi,
    I want to replicate an outbound delivery in the target system  through IDOC.
    but when i use standard IDOC Message type DESADV alongwith standard output type LALE, then it does'nt get replicated and an Inbound delivery gets created instead in the target system.
    I also used  another alternative of using BAPI with Business object 'LIKP' and  BAPI  BAPI_OUTB_DELIVERY_SAVEREPLICA
    but its not getting triggered may be coz m using the application program and routine in the Nace as RSNASTED only.
    Do i have to use any other program in NACE with Z O/P type for the same if i use BAPI. If so then what shud be the program name and Routine name for the same.
    Please help me to meet the above requirement with the appropriate aaproach.
    A quck reply is highly appreciable.
    Regards,
    Manoj

    Hi Manoj,
    Message type WHSORD is used transmit data to 3rd party whenever Outbound delivery is created in SAP i.e. as Outbound IDoc.
    I am trying to understand the issue and slightly confused.
    Is both sender & target systems are of SAP (SAP to WMS/EWM/SCM).
    Message type SHP_OBDLV_SAVE_REPLICA  which calls the BAPI you have already tried should work as I read from
    below document. 
    [SAP document link|http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/56a89d90-0201-0010-97a7-c5e8dbbb22e2?QuickLink=index&overridelayout=true]
    Please check if it can be useful.
    Regards,
    SG.

  • How to trigger automatically an IDOC and RFC from SAP R/3 system?

    Hi ,
    lets say if we are implementing IDOC to FILE &RFC to FILE scenario ,how can we trigger  on timely basis(schedules)
    1)standard IDOCs and BAPIs?
    2)customized Idocs and Customized Bapis?
    3)Master Idocs and transactiona Idocs?I think we need to use change pointers for master Idocs and donno about Transactional Idocs.
    please explain ,
    thank you very much for your help.
    regards,
    Babu

    sorryfor the late reply, I was busy with my work.thank you for your posts.
    so all of you say just run the RSEOUT00 no matter what interface we use in XI like Master ,transactional Idocs,standard or customized BAPIs?
    And I think we use RSNASTED if we have on recieving side right?
    <b>then when we would use a report of format below to trigger an RFC,is this format for Asunc RFC ?</b>
    REPORT Z_SEND_DATA_TO_XI.
    parameters: dest like rfcdes-rfcdest default '(RFC Destination you defined in SM59)'.
    <<your other variable declaration and ABAP Code here>>
    call function 'ZXI_SEND_DATA'
    in background task
    destination dest
    exporting
    Name = John
    City = Smith. (The values to pass to XI)
    commit work.
    <<Any Write statements or sy-subrc statements here>>
    6) Save and Activate your ABAP program.
    6) After all these steps, execute your ABAP Program to send the data to file via XI.

  • Problem with user exit EXIT_SAPLIEDI_001 for Inbound Idocs in replacing G/L

    Hello all,
    I am currently facing an issue where my IDOC where exit EXIT_SAPLIEDI_001 is not appearing to work properly.
    Basically I am using the FM that processes the inbound idoc (IDOC_INPUT_INVOIC_FI) to post an accounting document. We needed a solution where we need to substitute one of the G/L Accounts.
    The current process in our SAP system is that we are creating a billing document which automatically generates the output type (running: program rsnasted subroutine edi_processing) to create and process the inbound idoc. 
    So I discovered FM EXIT_SAPLIEDI_001 which exports company code and G/L Account back does this.
    In this exit, Since I needed to get data from the IDOC, I used the logic ASSIGN: ('(SAPLIEDI)IDOC_DATA[]') TO <fs_edidd> to get the DATA Records for further processing.
    During the development and testing phase in the Sandbox system this works.
    However when we moved this to production we encountered a situation where the G/L account was not being substituted so were assuming EXIT_SAPLIEDI_001 is not working properly. However when I reprocess this in production either by running the idoc with errors RBDMANI2 or BD87 the IDOC is properly posted and the G/L Account is substituted as well as if I try to repeat the output type of the billing document. So there are instances when in the actual business scenario it does not work except when I reprocess it.
    I was wondering if there are any ideas why this could have happened?
    Oh ... I  also noticed when we transported the objects of the exit. When I try to double click the subroutine I made inside the exit it said the object does not exist. I had to generate the function group of FM EXIT_SAPLIEDI_001 in SE80 in production for it to reflect. I was wondering if this could have caused the issue.
    Well I hope to hear from you.
    Regards
    Edited by: Rob Burbank on Dec 6, 2011 1:03 PM

    Hi,
    Check in t.code CMOD whether project is active or not (Activate the Project)
    BR,
    Vijay

  • Outbound Sales Order - want to restrict line items

    Hello,
       I  am generating outbound Idocs, from sales order (using ORDRSP) , via message control. (RSNASTED - EDI_PROCESSING)
       I have 4 line items in my order, where, item 20, 30, 40 are components(parts) of item 10.  In technical terms VBAP will have UEPOS 000000 for item 10, and 000010 for items 20, 30 and 40. (as 10 is parent item for 20, 30, and 40).
      I need my idoc with just item 10. ie, I dont want items 20, 30, and 40 in my Idoc.
      Which will be the best way to restrict this ?  I have user exits EXIT_SAPLVEDC_001, which have Tables XVBAP in interface in FM IDOC_OUTPUT_ORDRSP.   Shall I go ahead with this user exit or is there a better approach ?  
    Please share your thoughts.
    Thanks

    Hi,
    It would be better to use user exits EXIT_SAPLVEDC_002 in FM IDOC_OUTPUT_ORDRSP to delete the unneeded segments in table INT_EDIDD instead of mess around table XVBAP.
    Regards,
    Ferry Lianto

Maybe you are looking for