FI-Idoc2File: We20 Configuration

Hi,
For IDoc to File scenario , I have checked in T - code NACE but no entry is there for FI - Idoc, Please suggest below details for Outbound IDOCs
IDOC --- FIDCC1.FIDCCP01
*We20 --> Outbound Parameters --> Message Control*
Application - ???
Message Type- ???
Process Code - ???
Thanks.

HI ,
Hope This will help you.
Message Type  FIDCC1
Inbound Event Code  FID1
Function     IDOC_INPUT_FIDCC1
Check this transection code to help youself.  WE42
It will tell about the  a proper/relevent process code for the inbound idoc in the partner profile.
Regards
Prabhat Sharma.

Similar Messages

  • Idoc2File- WE20 Configuration Details

    Hi,
    The scenario is IDoc to File , Please suggest  below details for Outbound IDOCs
       IDOC --- REMADV.PEXR2002
       IDOC --- MBGMCR.MBGMCR03
    *We20 --> Outbound Parameters --> Message Control*
    Application -         ???
    Message Type-    ???
    Process Code -     ???
    Thanks,

    Hi,
    Below T-codes can help you find information:
    Check Transaction NACE to see what applicatios you can use for different objects.
    Check transaction WE42 for all inbound process codes
    Check transaction WE41 for all outbound process code.
    Check transaction WE64 for inboud / outbound message types and related process codes.
    Not sure if any standard process codes are avaialable for the mentioned outbound idocs.
    Post you question in other forum like MM / SD .

  • Standard IDoc processing in XI (WE20)

    Dear experts,
    when an IDoc is sent to XI, it's visible in transaction IDX5 and SXMB_MONI or Runtime Workbench. It's processed based on Integration Repository and Integration Directory configuration.
    Is it possible to enable standard IDoc processing in ABAP in an XI system? With standard I mean, that the IDoc is stored to EDIDC, EDID4 and EDIDS and processed based on WE20 configuration and processing code etc.
    How does XI know, that the IDoc should be passed to Integration Engine instead of being processed by an function module like in other SAP systems?
    Thanks and regards,
    David

    Hi,
    >>>Is it possible to enable standard IDoc processing in ABAP in an XI system?
    yes it is
    >>>How does XI know, that the IDoc should be passed to Integration Engine instead of being processed by an function module like in other SAP systems?
    if you want to see it in WE20 in PI you just need to put it in the exception table (idoc name) and this is it ,
    it will not be processed by the IE
    REPORT - IDX_SELECT_IDOCTYP_WITHOUT_IS
    Regards,
    Michal Krawczyk

  • Collecting IDOCs in BPM

    Hello BPM experts,
    I needed some help with one of the scenarios with BPM.
    We are sending outbound IDOCs from ECC to PI (v7.0 SP14)
    Step 1 - Process kicks off from ECC.
         1.There are multiple partners in WE20(Configured in WE20) which sends out IDOCs through the single tRFC port(WE21).
    Step 2- XI starts to collect the IDOCs from these different partners in ECC(Configured in           WE20) using a wait step in ccBPM.
    Step 3-By using correlation,the collected IDOCs recieved from different partners are translated and send to File adapter in seperate files.
    Note:For example if there are 10 partners in WE20 which sends to 1000 IDOCs,these transactions grouped and translated into 10 files and finally transmitted to partner using file adapter.
    We tested the scenarios and it is working fine,In production we faced an issue with BPM processing larger number of messages.SAP asked to apply note 1147377 to resolve this issue with bigger load.
    My concern here is if the mapping for a particular partner fails,will this cause an issue to the rest of 9 partners ? Please give me your suggetions.

    Hi,
    It is wrong forum, please ask your questions to form : Process Integration (PI) & SOA Middleware
    Regards,

  • Print IDOCs

    Hi Experts,
    (I will post this question in ABAP forums also)
    I am a new SAP FI consultant and am not sure of how to overcome the situation I encountered, while trying to print the IDOcs generated during the payment run.  Without specifying any print variants in the APP parameters (tcode F110), I scheduled the payment run and noticed in the payment log that the required IDOcs were generated.
    Then, I used tcode se38 to execute the RFFOEDI1 program and specified the parameters to print the IDOcs.  I entered the run date, identification, company code info, house bank info, payment method, etc.  I had the "Generate SAP IDOc" box checked and specified the printer as LOCL, and had the "print immediately" box checked on.  I also made sure that under the tcode WE20 configuration, I had the "Transfer immediately" radio button selected.  In addition, I also entered the tcode WE05 to generate the list of the IDOcs generated.  In this list, I noticed a green color dot in the status field, which (I think) says that the information from the IDOc is transferred to the target system correctly.
    However, after executing the program RFFOEDI1, I got an error that says "WRITE_FORM is invalid, START_FORM is missing".  I think I need to talk to the ABAP programmers about this, but am not sure about that.  Do you think that this error should be resolved by the ABAP team?  Or is there anything that I can do to avoid this error?
    All your help is greatly appreciated.
    Thanks in advance for your guidance!
    Regards,
    V.SAPFICO

    Hi,
    Check which form you have assigned in the payment advice/ EDI Accompanying sheet.
    RFFOEDI1 can generate only these forms.
    Regards,
    Gaurav

  • EDI - Purchase Order

    Hello,
    I need to use EDI and IDOCs to transfer a purchase order directly from my ECC system to a business partner's system.
    I'm new to IDOCs, so I've been having some dificulties to customize the whole scenario. Do you know if there is guide I can follow? If not, can you please give a brief description of what I need to do to succeed?
    Thanks in advance.
    Regards,
    Ricardo

    Hi..
    Please check these steps..it will be helpful....
    [http://help.sap.com/saphelp_sm32/helpdata/en/dc/6b7c9f43d711d1893e0000e8323c4f/content.htm]
    Also you need to do settings for your third party business system
    1. SM59: Create RFC destination
    2. WE21: Create Port
    3. WE20 Configure Partner Profile.
    3. BD64: Create distribution Model.

  • Inbound IDOC receiver port not getting filled in

    Hi All,
    I checked the WE20 configuration and it is fine. Just wanted to check if there is any other sap configuration which might be missing.
    The IDOC is coming from a web server and they confirmed that they are filling the receiver port information while sending, but in the IDOC that we receive in SAP the receiver port is coming as blank.
    Any pointers will be appreciated.
    Thanks,
    Anil

    Hello Anil,
    When they say they are filling receiver port that means they filling EDIDC-RCVPRT, please note with out receiver port you will not be able to receive the Idoc.
    It means this value might be cleared somewhere in SAP. may be user exit or BADI or enhancement. what you can do is try to create inbound idocs by populating receiver  port using WE19 and check whether the created idoc contains this value or not.By doing the you can get an idea where this value is disappered.

  • XI/PI: Receiver IDOC adapter packaging

    Hi Experts,
    I have File to Idoc scenario. I am already doing idoc packaging using Michal's blog:- /people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
    In addition to this i want to send the idocs in batch rather them sending once. I have already explored the options using TCODE we20. In this we have an option of triggering the idocs using batch job. We can use this program RBDAPP01 to set the packet size.
    All i want to know is how activate and schedule this batch job.

    Hi Aditya,
    your msg heading is saying about reciver IDOC adapter packaging.........so i am little confused......
    You are asking about sending IDOCs from XI to R/3 or from R/3 to XI?
    i think you are asking about sending IDOCs from R/3 to XI - because the answer suggested by Michal is for sending IDOCs from R/3 to XI because WE20 configuration is done on R/3 server.......
    if you are asking about IDOC packaging from XI to R/3 system, then i think in XI by SXMB_ADM tranasction - Integration Engine configuration - there is a IDOC PACKAGING parameter which can be set which will send that many IDOCs from XI to R/3.
    Regards,
    Rajeev Gupta
    Edited by: RAJEEV GUPTA on Apr 3, 2009 3:07 PM

  • IDOC_INBOUND_FROM_FILE

    hi,
    i'm using IDOC_INBOUND_FROM_FILE to read the content of text file, then i want to convert it into idoc.
    But the idoc generate status is 64 and i want that their status is 51.
    can anyone help me......this is vey urgent

    Hi,
    Status 64 implies that the IDOC inbound processing is yet to happen and this is decided by the WE20 configuration given below.
    Go to WE20, and check for the logical system. against the logical system check for the message type and the idoc type that you have used for inbound posting.
    Then check if the immediate posting flag is ticked. This flag decides if the idoc will be posted immediately or through a scheduled batch job.
    Regards,
    Sravanthi

  • G/Laccounts IDOCS error status 29

    Hi all,
    I  transfer G/L accounts from a sap source system to another sap system, using transaction BD18 and message type GLMAST.   for some of the general ledger accounts , it  works very well.
    however, half of my accounts have a functional area (FUNC_AREA).
    when I send these accounts , I have the  status 29 : error in ALE service:  and the error is F5 162   , "business area & is not defined " .  I have no business area in my accounts , the value "business area" is filled  with the beginning of the value FUNC_AREA !
    What does means the error status 29 ?  is it really a "Missing or Incorrect Partner Profile" ?  In WE20 (configuration of partner profile), in  my source system I have GLMAST for outbound parameter , and in my reception  system, I have GLMAST in the inbound parameter, this is the standard and should be correct ... What do I have to do in order to correct this status ?
    Does anyone have any ideas? Thanks in advance.

    Hi sabine,
    Your configuration should like below.
    A -- Sending SAP system
    B --  Receiving SAP System
    In  A ,   go to we20.
    Click on system B( Partner type LS).
    Now in "Outbound parameters" , your entry should be maintained.
    Thanks
    Jitendra

  • Regarding Message Interfaces

    Hi Guys,
    I am new to SAP XI. Only thing I know is Message Interfaces are very key role to play in SAPXI. In case of any IDOC Are BAPI you can directly import them to I.R as interface objects. for example there are lots of IDOCS Available like BATMAS, MATMAS, ORDERS, CREMAS, there is lot of confusion on this what information this IDOCS contain how can we Know that particular IDOC contains the information Meeting our requirement.  In case I am integrating MM Module Are SD module with SAP what interfaces I need to use  pls any one explain me with clear scenario. and also pls help with some realtime docs so I can understand the things better. Thanks in advance.
    Regard's
    Kiran.B

    Hi Kiran,
           There is no confusion about IDOCs.  The requirement  shows the what type of IDOC u want to used.
    The XI guys will take care of the Import the IDOC from particular R/3 system.
    Like same RFC Function Modules also..
    When ever we used IDOC we need configured setting in R/3 & XI Systems.
    __Configured steps in  R/3 System:__
    1) RFC Destination-- SM59
        --> Create the RFC Destination
       --->Crate the RFC Destination type 3(R/3 system)
       ---> specify the server address of the Integration server as target hosts
    2) Port----WE21
       _---->Create the port for transaction RFC
    > Enter the RFC Destination
    3) Partner Profiles--WE20
    Configure the steps in XI System:
    1) Create the RFC destination (SM59)
    2) Create the IDOC port into IDOC adapter(IDX1)
    3) Load the meta data of IDOC into IDOC Port(IDX2)
    Regards,
    Nskumar

  • RSNAST00 Concern?

    Hi..
    I want to know how RSNAST00  calls the respective function module in the ABAB Coding.?
    For Example in case of say any Delivery Document Number, when we run RSNAST00 for it giving the proper message type(say in our case LD00 with ALE as a medium)then at what point of time is the function module (say IDOC_OUTPUT_DELIVRY)called in that program. I didnt see a direct call of the function module as such in the program.
    I hope I have made myself clear in framing a question.
    Thanks.

    Hi Subhash,
    As most of reply said, RSNAST00 will call the subroutine ALE_PROCESSING or EDI_PROCESSING in the program RSNASTED. But this is link is defined in your message determination .. If you know place where you maintain the Program name script name for Printing the documents with output type.. it is the same place you maintian the subroutine and program (i.e. ALE_PROCESSING or EDI_PROCESSING in the program RSNASTED based on the output medium; A- Ale, 6-EDI).
    So when you run RSNAST00, it basically selects all the output records ready for procesing from NAST table based on the seletion parameters you have give. From there it identifies the program and subroutine to be called, calls that particular subroutine (for printing it will be your ENTRY subroutine in Driver program) with the Nast record. RSNAST00 Job is done once it calls the subroutine..
    Now the Subroutine being called takes the job of printing/faxing/ creating & sending the iDoc.
    In case of ALE/EDI, your ALE_PRocessing & EDI_procssing routine determines the FM to be called in the following way.
    It picks up the Message partner from the NAST record and check whether there is partner profile defined for that in WE20. If not defined error.. if defined, it will determine the FM to be called based on information given in the Output control tab and processed code give there (Process code is linked to your FM that fill the iDoc). Then it passes the iDoc internal table to ALE layer for further processing which stores that on DB and sends it our bsed on the WE20 configuration..
    Hope this gives you the clear picture about how the iDoc is generated from output control.
    Regards,
    Nagaraju Chidurupalli.

  • Printing IDOcs

    Hi Experts,
    (I will post this question in SAP FI forums also)
    I am a new SAP FI consultant and am not sure of how to overcome the situation I encountered, while trying to print the IDOcs generated during the payment run.  Without specifying any print variants in the APP parameters (tcode F110), I scheduled the payment run and noticed in the payment log that the required IDOcs were generated.
    Then, I used tcode se38 to execute the RFFOEDI1 program and specified the parameters to print the IDOcs.  I entered the run date, identification, company code info, house bank info, payment method, etc.  I had the "Generate SAP IDOc" box checked and specified the printer as LOCL, and had the "print immediately" box checked on.  I also made sure that under the tcode WE20 configuration, I had the "Transfer immediately" radio button selected.  In addition, I also entered the tcode WE05 to generate the list of the IDOcs generated.  In this list, I noticed a green color dot in the status field, which (I think) says that the information from the IDOc is transferred to the target system correctly.
    However, after executing the program RFFOEDI1, I got an error that says "WRITE_FORM is invalid, START_FORM is missing".  I think I need to talk to the ABAP programmers about this, but am not sure about that.  Do you think that this error should be resolved by the ABAP team?  Or is there anything that I can do to avoid this error?
    All your help is greatly appreciated.
    Thanks in advance for your guidance!
    Regards,
    V.SAPFICO
    Moderator message: please do not cross-post.
    Edited by: Thomas Zloch on Jan 3, 2011 1:54 PM

    Hi,
    What do you mean by "printing to printer from an idoc"..??
    Let us kno what type of idoc is it?? what is it supposed to do when processed succesfully.
    This will help us understanding your problem better and help you.
    Regards,
    SB
    Edited by: Satish Bharambe on Jul 12, 2011 6:58 PM

  • EDI requirements

    Hi Experts,
    My client wants to use EDI to transmit PO to Vendors.
    What are the basic requirements to use EDI functionality in client place and vendor.
    Do the vendor need to have SAP? If not SAP what software or hardware vendor needs to have to recieve EDI Docs.
    Also what my client need to have other than SAP  to send doc by EDI to vendors.
    Thanks in advance.
    Warm Regards
    NDS

    hi,
    check the link:
    [Send PO via EDI|http://help.sap.com/erp2005_ehp_04/helpdata/EN/dc/6b7c9f43d711d1893e0000e8323c4f/content.htm]
    Shortly:
    1. SM59: Create RFC destination.
    2. WE21: Creation of  Port
    3. WE20 : Configure Partner Profile...
    4. BD64: Create distribution Model...
    The system generates an IDoc of type ORDERS01...
    Regards
    Priyanka.P

  • Regarding QM interfaces

    Hi All,
    I have to develop QM interfaces...The Scenario is as below.. Please guide me how to proceed
    1. Once inspecton lot completed, data has to go to external system in table format.
    2. After that results recording and UD has taken care in the external system
    3. Once results are updated with ok, UD has to update automatically in the SAP system
    4. In case of rejection, defects will send to SAP system and based on defects need to update Notification in SAP system
    5. After that notification need to send to External system.
    6. I have to send master data like characteristics, Catalogs, sample procedures and sample scheme
    Pls help me how i have proceed....
    I already check with QM-IDI interfaces, but Results updation and UD updation and Notification updation will automatically done, this purpose will solve.
    If it solves pls provide me the techniqes to handle these QM-IDI secenarios...
    Regards,
    ReddyNara

    Hi Kiran,
           There is no confusion about IDOCs.  The requirement  shows the what type of IDOC u want to used.
    The XI guys will take care of the Import the IDOC from particular R/3 system.
    Like same RFC Function Modules also..
    When ever we used IDOC we need configured setting in R/3 & XI Systems.
    __Configured steps in  R/3 System:__
    1) RFC Destination-- SM59
        --> Create the RFC Destination
       --->Crate the RFC Destination type 3(R/3 system)
       ---> specify the server address of the Integration server as target hosts
    2) Port----WE21
       _---->Create the port for transaction RFC
    > Enter the RFC Destination
    3) Partner Profiles--WE20
    Configure the steps in XI System:
    1) Create the RFC destination (SM59)
    2) Create the IDOC port into IDOC adapter(IDX1)
    3) Load the meta data of IDOC into IDOC Port(IDX2)
    Regards,
    Nskumar

Maybe you are looking for