ALE IDoc : Vendor Master : Cremas: Inbound IDocs are bypassing the Customiz

Hi,
Create Vendor master inbound IDocs - CREMAS - are overridding the customizing settings.
For example for a particular vendor group a number range is set in customizing.
When we try to create a vendor through XK01 which does not fall in a particular number range as set in customising for a particular vendor group, we get a error message and creation is terminated.
But if the same vendor is created via standard idoc CREMAS, vendor is created without any errors bypassing the customizing settings.
So can anybody help me in this. Is there any customising setting that we need to do explicitly for Vendor IDocs. Or any other setting in standard IDoc.
Thanks in advance.

Hi,
1. If your vendor changes should be updated from one system to other system through ALE, we need to active the change pointers.
2. Change points can be activate through Tcode SALE
3. After activating change points and your distribution model is ready, you can execute the program RBDMIDOC to genarate the IDOCs.
4. Normally this program will be executed in the background
5. And as you said, you have to do some validations before sending IDOCs. For this you can Filters and rules in the DM.
OR you can write the code in user-exists of outbound posting program.
Rewards if this info is useful.
Thanks,

Similar Messages

Full Master Data Distribution in ALE - Vendor Master CREMAS(Full Distributi

Hi Experts,
   I have to do a Full Master Data Distribution in ALE - Vendor Master CREMAS(Full Distribution) using BD21.
   I have already read the blog of Mickel and incorporated the code in Change_Pointer_Read.
   It is still not working. Should I include the code at the end of the Function Module. If yes, how to code at the last as
   I can include my code at the SAP suggest Enhancement and End Enhancement.
   Is there any way I can create the implicit Enhancement at the end of the Function Module.
   I will appreciate any help to make the Full Distribution work.
Thanks,
Mich

Hi,
   Here is the link.
   /people/michal.krawczyk2/blog/2009/06/04/distribution-of-full-master-data-objects-from-change-pointers
   My requirement is to send the whole Vendor Master in a IDoc even though for eg there is only one field change in address field of Vendor Master. Full Master Data distribution. But the program BD21 creates only IDocs with segments where the changes are made in the particular tab like address.
   Is there any Enhancement or way to enforce the whole Master Data(CREMAS) to be distributed.
   I will really appreciate any helpful answer .
Thanks,
Mich

Create Article Master through inbound IDoc (Normal Flow of Inbound IDOC)

Hi All,
I am new to Inboud IDoc.
I have a file on application server. In program (SE38), I read that file through "open data set"..." close data set.". now the file is in internal table. where should i pass that data (i mean in which structures). and what should i do to create an article in SAP System. I mean what should i write in program ? which Fn. module called ? etc..
My requirement is that using Inbound IDoc ARTMAS05 post the data from application server.
I am aware of all ALE configuration and all WE30, WE31, WE81, WE82.....
could anyone brief the basic steps of inbound IDOC ARTMAS05 and INFREC01.
please help me out.
valuable contribution is appreciated.
Thanks & Regards,

for this you need to write a program .
once you get the data form file to Internal table. then
pass your internal table data to idoc control and idoc dta
like pass all segemnts data then pass all segments data to this FM
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
      EXPORTING
        master_idoc_control            = wa_edidc
      TABLES
        communication_idoc_control     = gt_edidc
        master_idoc_data               = gt_edidd

How to handle the master data when we are loading the from multiple clients

Hi,
We are loading HR data from two different clients 101 and 102 of same source system.
Here we are facing the problem with msater data maintenance for employee in BW, whose employee numbers are same.
For example client 101 employee range is 10001 to 10100.
In client 102 also same employee range.Then how to handle the above scenario
Is there any solutions apart from compounding of infoobjets with logical system.
Thanks in advance for your sugessions.
Thanks.
Maria.

Hi ,
you can create copy of 0EMPLOYEE Object.
Load one client master data to the copied object.
Example:
1. Create ZEMPLOYEE copy of 0EMPLOYEE.
2. create the transformation or rules
3. You have to follow same for remaining objects
regards,
HREDDY

Vendor Master Creation through IDoc with Multiple Company Codes

I am trying to create vendor masters sent from a 3rd party into SAP using CREMAS05 IDoc. I have the requirement that the vendor should be created in each of 3 company codes and the vendor number is internally assigned in SAP.
I create my IDoc with the general data E1LFA1M and multiple E1LFB1M & E1LFB5M Children. When I post the IDoc using IDOC_INPUT_CREMAS which uses Call Transaction, the vendor gets created for the first company code, but the IDoc errors on the vendor extension XK01 for the next company code with the error: "Fill all required fields SAPMF02K 0111 ADDR1_DATA-NAME1".
In debugging through this, it appears that the vendor number that gets created in the first XK01 transaction does not get passed into the data for the second XK01 call and SAP tries to create a new vendor instead of extending the newly created one.
If I force the value in during debug after the initial call transaction into the variable h_lifnr, it works fine (Vendor created with multiple company codes.
Any help would be greatly appreciated.
-Larry

I cannot give you exact solution, but can guess why this is happening, below is what I believe.
I think Synchronous update is not happening in call transaction, second transaction is getting processed before the first one is saved, debugging it works fine, because we give system enough time to save while processing.
Generally in call transaction we have MODE, if we pass S - then synchronous update happens, in your case, you need to find the way to incorporate this.
Hope it helps.
Regards,
Ravi Kishore.

Vendor Master classifications using IDoc CLFMAS

I am using the IDoc message type CLFMAS, basic type CLFMAS01 and I set my source multi structures as follows:
ZCLASS_HDR
 HDR C(005) Header Id :<HDR>
 MAFID C(001) Assignment category: 'O'
 OBJEK C(050) Vendor number:'5000101'
 CLASS C(018) Class no. :'BEE-VENDORS'
 KLART C(003) Class type :'010'
 DATUV C(008) Date :sy-datum
 OBJECT_TABLE C(030) : 'LFA1'
 ZCLASS_DTE
 DTE C(005):<DTE>
 ATNAM C(030):'BEE_Senior_management'
 ATFLV C(016):'10'
 ATWRT C(030):'10'
where the bold represent the header structures and the values after the colon.
When I process the IDoc I get the following error:
Object 5000102 (LFA1 ) not found, the vendor number 5000102 is in table LFA1. Can anyone please tell me what I am doing wrong here?
Rgds
George

Hi George!
Try with leading zeros: ZCLASS_HDR-OBJEK = '0005000101'. (In total 10 chars). You can use FM CONVERSION_EXIT_ALPHA_INPUT to do the conversion.
Regards,
Christian

Trigger Vendor master idoc automatically

Hi Experts,
When i save idoc vendor master (CREMAS05) , how can i trigger the idoc and send it to XI system automatically ?
I tried running the report RSEOUT00 with the idoc details but message displayed is 'no idoc ready for processing'.
Regards,
Syed.

Hi
First you test the scenario by generating the IDoc with Tr. code WE19 and execute Standard Outbound processing.
Have u checked whether that Idoc is generated or not?
Go to WE02 and check the status of the Idoc.
Regards
Sridhar Goli
Edited by: Sridhar Goli on Sep 30, 2008 1:47 PM

Step-by step procedure for INBOUND IDOC (VENDOR CREATE / CHANGE)

Hi ,
Can any body provide me the step-by-step procedure for Inbound IDOCS.
As i'm new to this i need the the clarification between Inbound & outbound idocs.
How can we differentiate both?
where to define outbound & where to define Inbound?
( If possible Please explain me the procedure for Vendor Create through INBOUND IDOCS )
Thanks in advance..

Hi,
Ale Technology is SAPu2019s technology to support distributed yet integrated processes across several SAP systems.
Outbound Process:
ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.
1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.
2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.
3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.
4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.
Inbound Process:
The inbound process receives an IDoc and creates a document in the system.
1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.
2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.
3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.
Over view of IDocs:
IDoc is a container that is used to exchange data between any two processes. The document represented in an IDoc is independent of the complex structure SAP uses to store application data. This type of flexibility enables SAP to rearrange its internal structure without affecting the existing interface.
IDoc interface represents an IDoc Type or IDoc data. IDoc Type represents IDocu2019s definition and IDoc Data is an instance of the IDoc Type.
IDoc Types:
IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
An IDoc is an instance of an IDoc Type and consists of three types of records.
i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
Message in IDoc Type:
A Message represents a specific type of document transmitted between two partners.
Outbound Process in IDocs:
Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
The Customer Model:
A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
Message control:
Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.
Change Pointers:
The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
IDoc Structure:
A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
Selection Program:
Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection programu2019s design depends on the triggering mechanism used in the process.
Filter Objects;
Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
Port Definition:
A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
RFC Destination:
The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
Partner Profile:
A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDocu2019s packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
Service Programs and Configuration Tables:
The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
Process flow for Distributing Transactional Data:
Transactional data is distributed using two techniques: with Message control and without message control.
Process flow for Distributing Master Data:
Master data between SAP systems is distributed using two techniques: Stand alone Programs and Change Pointers.
Triggering the Outbound Process via Stand-Alone Programs:
Stand-Alone programs are started explicitly by a user to transmit data from one SAP system to another. Standard Programs for several master data objects exist in SAP. Ex. The material master data can be transferred using the RBDSEMAT program or transaction BD10.
The stand-alone programs provide a selection screen to specify the objects to be transferred and the receiving system. After the stand-alone program is executed, it calls the IDoc selection program with the specified parameters.
Triggering the Outbound Process via Change Pointers:
The change pointer technique is used to initiate the outbound process automatically when master data is created or changed.
A standard program, RBDMIDOC, is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process for distributing the master data to the appropriate destination. The RBDMIDOC program reads the table TBDME to determine the IDoc selection program for a message type.
Processing in the Application Layer:
The customer distribution model is consulted to make sure that a receiver has been defined for the message to be transmitted. If not, processing ends. If at least one receiver exists, the IDoc selection program reads the master data object from the database and creates a master IDoc from it. The master IDoc is stored in memory. The program then calls the ALE service layer by using the function module MASTER_IDOC_DISTRIBUTE, passing the master IDoc and the receiver information.
Processing in the ALE Interface Layer:
Processing in the ALE Layer consists of the following steps:
u2022 Receiver Determination: The determination of the receiver is done through Customer Distribution Model.
u2022 IDoc Filtering: if an IDoc filter is specified in the distribution model for a receiver, values in the filter are compared against the values in the IDoc data records. If a data record does not meet the filter criteria, it is dropped.
u2022 Segment Filtering: For each sender and receiver combination, a set of segments that are not required can be filtered out.
u2022 Field conversion: Field values in data records are converted by using the conversion rules specified for the segment.
u2022 Version change for segments: Segments are version-controlled. A new version of a segment always contains fields from the preceding version and fields added for the new version. Release in IDoc type field of the partner profile to determine the version of the segment to be generated.
u2022 Version change for IDocs: IDocs are also version controlled. The version is determined from the Basic Type field of the partner profile.
u2022 Communication IDocs generated: The final IDoc generated for a receiver after all the conversions and filtering operations is the communication IDoc. One master IDoc can have multiple communication IDocs depending on the number of receivers identified and the filter operations performed. IDoc gets the status record with a status code of 01 (IDoc Created).
u2022 Syntax check performed: IDoc goes through a syntax check and data integrity validation. If errors found the IDoc get the status of 26 (error during syntax check of IDoc u2013 Outbound). If no errors found the IDoc gets the status 30 (IDoc ready for dispatch u2013 ALE Service).
u2022 IDoc dispatched to the communication Layer: In the ALE process, IDocs are dispatched using the asynchronous RFC method, which means that the sending system does not await for data to be received or processed on the destination system. After IDocs have been transferred to the communication layer, they get a status code 01 (Data Passed to Port OK).
Processing in the Communication Layer:
To dispatch an IDoc to a destination system, the system reads the port definition specified in the partner profile to determine the destination system, which is then used to read the RFC destination. The RFC destination contains communication settings to log o to the remote SAP system. The sending system calls the INBOUND_IDOC_PROCESS function module asynchronously on the destination system and passes the IDoc data via the memory buffers.
Inbound Process in IDocs:
An inbound process used IDoc structure, posting programs, filter objects, conversion rules, a partner profile, service programs, and configuration tables to post an application document from an IDoc.
Posting Program:
Posting programs, which are implemented as function modules, read data from an IDoc and create an application document from it. A posting program exists for each message. Each posting program is assigned a process code. A process code can point to a function module or a work flow. In the standard program process codes always point to a function module.
Ex. The posting program for message type MATMAS is IDOC_INPUT_MATMAS which has a process code MATM.
Workflow:
A workflow represents a sequence of customized steps to be carried out for a process. The workflow management system is used to model the sequence, identify information required to carry out the steps and identify the person responsible for the dialog steps.
Partner Profile;
A partner profile specifies the components used in an inbound process (partner number, message type, and process code), the mode in which IDocs are processed (batch versus immediate), and the person to be notified in case of errors.
Process flow for the Inbound process via a Function Module:
In this process, IDocs are received from another system and passed to the posting function module directly.
1. Processing in the communication Layer:
The IDOC_INBOUND_ASYCHRONOUS program, triggered as a result of an RFC from the sending system, acts as the entry point for all inbound ALE processes. The IDoc to be processed is passed as an input parameter. Control is transferred to the ALE/EDI layer.
2. Processing in the ALE/EDI Interface Layer:
u2022 Basic integrity check: A basic integrity check is performed on the control record.
u2022 Segment Filtering and conversion: Filtering out unwanted segments and carry out any required conversion of field values.
u2022 Creation of Application IDoc: The application IDoc is created and stored in the database and a syntax check is performed. If there are errors it gets status code of 60 (Error during Syntax check of IDoc u2013 Inbound). At this point a tangible IDoc, which can be monitored via one of the monitoring transactions, is created and the IDoc gets status code 50 (IDoc Added).
u2022 IDoc Marked ready for Dispatch: IDoc gets the status code 64 (IDoc ready to be passed to application).
u2022 IDoc is passed to the posting program: The partner profile table is read. If the value of the Processing field is set to Process Immediately, the IDoc is passed to the posting program immediately using the program RBDAPP01.
3. Processing in the Posting Module:
The process code in the partner profile points to a posting module for the specific message in the IDoc. The posting program implemented as a function module either calls a standard SAP transaction by using the Call Transaction command for posting the document or invokes a direct input function module.
The results of execution are passed back via the function moduleu2019s output parameters. If the posting is successful IDoc gets the status code 53 (Application Document Posted) or it gets status code 51 (Error: Application Document Not Posted).

Inbound IDOC for Invoice failing at segment-E1EDK28- Incorrect BankAccNumbe

Hi SDNers,
We have EDI - Invoice/Invoice Processing.
Inbound Idoc failing at segment E1EDk28.
This is because in segment E1EDK28 ,
1. The field ACNUM has the value for Bank Account Number as N111111A.
2. This is incorrect.
3. This field should have had the value for account number as 0000N111111A.
4. But for some reason the pre-zerou2019s are removed .
5. When we check the process code IDOC_INPUT_INVOIC_FI, and IDOC_INPUT_INVOIC_MM, and the table LFBK the value is saved as 0000N111111A.
But why in IDOC it is getting seen as N111111A?
Please guide as to where i need to look for the solution or fix.
Where should i look for the fix for this issue.
Regards,
SuryaD.
Edited by: SuryaD on Nov 24, 2009 7:01 PM
Edited by: SuryaD on Nov 25, 2009 9:21 AM

Hi Navitha,
Thanks for your response.
I had checked the exits to see if the field ACNUM is changed anywhere while debugging.
It wasn't getting changed anywhere.
In fact the user and the ticket creator had the assumption that the Vendor Bank Account number (in case of the Inter company billing) is maintained in vendor master (XK03) or LFBK or KNBK.
the y thought IDOC is picking the ACNUM from one of the above three place.
They were checking the Bank account number from the above 3 places and since here it was maintained as 0000N111111A while in IDOC it was showing as N1111111A they had all this confusion.
In fact the IDOC segment E1EDK28 picks the ACNUM from SPRO->Financial Accounting-> Banking->home bank.
Here we checked and found that the Bank Account Number was maintained as N1111111A and we changed it to 0000N1111111A and the IDOc segment E1EDK28 picked it correctly.
Issue got resolved.
Thanks for your input.
Regards,
SuryaD.
Edited by: SuryaD on Nov 25, 2009 10:29 PM

Trying to change Inbound IDOC to Outbound IDOC for testing....

Hi Friends,
I am trying to do the following
1) In our legacy system SAP R/3 3.1H we have received an IDOC from our partner. This has been stored correctly.
2) We now need the same functionality in our SAP R/3 4.6C system so I have created the IDOC type + segments accordingly. I have also set up the partner profiles
3) We need test data but our partner can not send yet so the only other way is to send this INBOUND IDOC from 3.1H to 4.6C.
4) HOWEVER, i have tried everything to do this like using WE19 to edit the idoc, but I can not process it for OUTBOUND processing.... You can in 4.6C but there is no option in 3.1H.
HELP!! Rewards

Hi Friend,
        The test programs allow you to skip certain sections of the processing chain between applications to localize errors. However, they can also be used to simulate an entire business process (for example, purchase order on the customer side with posting of the purchase order on the vendor side) in an SAP System (without any other systems). For this reason, the test programs are an important tool for configuring the IDoc Interface and defining new IDoc types.
Use
You can use the test tool to generate an IDoc manually and send the IDoc for either inbound or outbound processing. You are not restricted to a specific port type. You can start with an IDoc type (an empty IDoc) or use an old IDoc as a template and edit the IDoc, that is, add segments or change data. This is a good way to test new IDoc types, in particular.
You can forward your new IDoc for standard inbound processing (checking partner profiles and so on). You can also call a function module directly. You can therefore test new function modules for new IDoc types.
Activities
·        Start the test tool with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Test Tool (WE19). You can use a template for your test IDoc.
You can choose IDoc types as a template, either directly or according to a specific message type. You can use the F4 Help for IDocs used as a template, which searches for IDocs by selection criteria, in the same way, for example, to IDoc Display. When an IDoc file is used as a template, the IDocs are read from this file and are available to you for selection. A default value for the IDoc file gives you the system using your test port which you can enter in IDoc Administration . This test port must therefore be of the file type. The default file is the inbound file entered there.
·        You generate the IDoc using .
The IDoc is displayed as a tree structure. If you do not use a template to create the IDoc type, at least one more segment must be added.
·        To create segments in the form of tree nodes (colored fields) place the cursor on an existing node (for example a control record at the top) and choose .
You can cut, paste or copy individual segments or entire segment groups by positioning the cursor on the relevant segment and selecting the required action from the Edit menu.
·        Click on the white fields to change data in the segments.
In the case of the control record, only the fields which are relevant for standard inbound processing are displayed. Do not forget the required entries in the partner profiles if you want to send the IDoc for standard inbound processing! You can also change all of the control record data by choosing All fields in the edit screen.
In the All fields editor screen you must enter the non-language specific partner function (for example AG for vendor). This is the only screen in the IDoc Interface in which the partner function is not translated into your language (in English AG becomes vendor VD) - in the partner profiles or in the IDoc display the field is always translated. Thus, you see the partner functions here in the way they are saved in the database. This is a unique value in the SAP System and therefore protected against mistakes.
·        The additional procedure depends on whether you want to test inbound or outbound processing.
Test: Outbound Processing from MC
Use
Use this test program if you have chosen the Message Control module and want to test generation of an outbound IDoc from an existing message status record (table NAST).
Prerequisites
You must be able to post the application documents which are to be converted into IDocs by the Message Control module correctly so that a message status record can be generated. In the case of the Materials Management (MM) and Sales and Distribution (SD) components, the following entries are required:
·        Customer or vendor records
·        Material records
·        Info records
·        MC condition record: The output medium 6 (for EDI) must be entered here. The condition records are maintained as messages from the respective application.
The appropriate file ports and partner profiles must exist in the IDoc Interface.
Outbound processing must be stopped when the message status record has been generated to allow the test program to intervene. To do so, you must set the Message Control dispatch time to 1 (output with selection run) in the corresponding condition record in the application. This test program, therefore, is simply used to start a selection run which retrieves the Message Control records and sends them for further outbound processing. The program is report RSNAST00, which is also generally scheduled with dispatch time 1 in live operation.
Activities
Once the application document has been posted, outbound processing stops after the message status record has been generated and is triggered again by the test program. Choose SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Outbound ® Outbound from MC.
Errors are stored in the Message Control processing log (document header) and in the status records of the IDocs. The status records, however, are only available if the IDoc was successfully generated.
Use
This test program selects one or more outbound IDocs and forwards them to the external system. You can choose the IDocs according to various criteria (for example, recipient or business message).
Prerequisites
You require outbound IDocs which were generated without errors (no error status). The partner profiles, therefore, must be maintained completely.
Outbound processing must stop when the outbound IDocs have been generated to allow the test program to intervene. You can check this by setting the output mode to Collect IDocs in the partner profile for the IDoc Interface. If you now generate an outbound IDoc for the partner (for example, using the application or the test tool), the IDoc is only generated in the SAP System and is not forwarded to the external system. This test program, therefore, is simply used to start a selection run which retrieves your IDoc(s) and sends them to the external system. The program is report RSEOUT00, which is also generally scheduled with the output mode Collect IDocs in live operation.
Activities
You start the test program by choosing SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Outbound ® Outbound from IDoc (WE14).
You can decide whether the output mode is set to Start subsystem or Do not start subsystem in the partner profile. This defines whether the external (sub) system processes the IDocs further.
Use
This program is used to test whether status confirmations for an outbound IDoc are sent correctly from the external system to the SAP System. The port type here must be set to File.
Prerequisites
A correct status file which can be generated by an EDI subsystem, for example, is required. The status file must refer to an existing outbound IDoc in the SAP System. You can also generate such a status file yourself.
The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type File in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
Features
The SAP System reads the status file. The IDoc number contained in the file refers to the outbound IDoc, to which the status confirmation relates. The confirmed statuses are credited to the relevant IDoc in the form of status records in the SAP System.
Activities
Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Status ® Edit Status File (WE17) and pass the inbound port, name and directory of the file. These entries overwrite the standard values which you have stored in IDoc administration using the test port.
Test: Inbound Processing: Modified Outbound File
Use
This program converts an outbound file with IDocs to a correct inbound file and sends the new file for inbound processing. The outbound file is not modified and can therefore be used more than once. The port type here must be set to File.
Prerequisites
You need a correct outbound file, for example, a file which is generated by the test tool or using a standard outbound processing. In this case, a port of the type File must be specified in the partner profile for the IDoc Interface, so that the IDoc(s) can be written to a file.
The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type File in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
Features
The program imports sender and recipient data as input parameters from the user. The program reads the IDoc file and changes the corresponding entries in the IDoc control record. The changed data is written to a second IDoc file at the operating system level.
Standard inbound processing is then triggered;
·        Reading the modified file
·        Generating the IDoc(s) in the SAP System
·        Processing in the application
Activities
Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Inbound ® Inb. Mod. Outb. File (WE12).
Set the sender and recipient data, as well as the outbound file and the inbound file to be generated (path and name). Your entries for the inbound file overwrite the standard values which you have stored in IDoc administration.
The recipient in this case is the SAP System. The port is used for identification purposes:
·        SAP (for example RSMITH
Test: Inbound Processing: Original Inbound File
Use
This program reads an inbound file and sends the file for inbound processing. If all data has been successfully read, the file is deleted.
Prerequisites
You require a correct inbound file. In this case, correct means that the:
·        Sender and recipient in the control record are correct
·        Direction in the control record is set to 2 (inbound)
·        Client in the control record and data records are correct or empty
The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type File in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
Features
The program reads the IDoc(s) from the inbound file and sends them for standard inbound processing (with processing within the application).
The file is deleted after being read successfully!
Activities
Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Inbound ® Inb. Orig. Inb.File (WE16) and pass the following data:
·        Inbound port
·        Name and directory of the file
These entries overwrite the standard values, which you have stored in IDoc Administration using the test port.
Thanks

Vendor Master Inbound Interface

Hi All,
Is there a FM that can be used in an inbound interface for the vendor master creation?
We are using an extension of CREMAS05 basic type.
Thanks in advance.

Hi,
Thanks for the reply, but the FM IDOC_INPUT_CREDITOR calls FM ERP_IDOC_INPUT_CREDITOR and it is checks for IDoc types. If the IDoc type is not CREMAS01 to CREMAS05 it raises an exception.
As we are using an extension of CREMAS05, the FM gives exception.
So we are looking for some other FM or BAPI.
We were not able to find any BAPI for Vendor master creation.
Any other solution?
Thanks in advance.

Customer/Vendor determination error INVOICE02 IDoc (SMG FD017)

We want to have a copy of all invoices in an other SAP systeem. We are using INVOICE02 IDoc. I am using the output method via a LS (logical system) link (not Customer KU). But now we get an error: Customer/vendor could not be determined for intermediate document 0000000000119869 in the other SAP system (receiver system). We give a few partnerfuntions through, like BP, but this doesn't solve the problem.
- How can this be solved?
- Is there a programm to send IDoc Invoice in batch modus?
With regards,
Frank
>>>>>> Complete message
Customer/vendor could not be determined for intermediate document 0000000000119869
Message no. FD017
Diagnosis
Several procedures are defined for determining the partner (customer or vendor):
1. The customer/vendor can send his/her account number (the account
 number in our system) in the address segment.
2. The customer/vendor can send his/her account number (our number at
 the customer or vendor) in the address segment.
3. Only the name in the address segment clearly identifies the
 customer/vendor. In this case you can create an allocation within
 intermediate document customizing (IDoc base -> Control -> Forward
 inbound).
4. The customer/vendor is determined using his/her bank details (only
 for the "INVOIC01" intermediate document type).
5. The customer/vendor is taken from the control record of the
 intermediate document.
For 1.-3.: One of the address segments with the partner functions
 "II", "RS", "SU", 'SE' ("INV_ID01"), or "RS" or
 "LF" ("INVOIC01") is used for determining the
 customer/vendor.
Procedure
Create the customer or vendor within Financial Accounting or maintain his/her bank details.
Create customer - Proceed
Customer bank details - Proceed
Create vendor - Proceed
Vendor bank details - Proceed
If the customer/vendor can only be determined using his/her name, create a record within intermediate document customizing with
logical address = name, application = "FI" or "MM" and physical target in the SAP system = customer number/vendor number.
Proceed
<<<<<<

Not applicable any more

Inbound idoc ordsp fm:IDOC_OUTPUT_ORDRSP

my problem is that idoc fails when it comes in as a response of ORDCHG when user changes the delivery date in PO outbound idoc triggers with message type ORDCHG. Vendor sends the response as a confirmation of order via inbound idoc message type ORDRSP. it fails at that movement and gives an error ME 790(material number differ from .............) it is comparing the value of segment E1EDP19 qualifier 001 field IDTNR with ekpo-matnr &ekpo-ematn.
NOTE: there is value in segment and it is correct value. but when inbound idoc fails it is taking blank value in fekpo and comparing with ekpo-matnr &ekpo-ematn and giving an error ME 790
and when we reprocess the same failed idoc without any changes in it via WE19 it posted successfully
one more thing i noticed in all failed idoc that segment E1EDK02 qualifier 002 not got populated which contains vendor acknowledgement number.
but when we reprocess it in WE19 without doing any changes it posted sucessfully.
thanks in advance.

You say that "when we reprocess the same failed idoc without any changes in it via WE19 it posted successfully". What about if you reprocess the same iDoc via BD87 ? If you are using the same Function Module, this shouldn't happen, unless you have some very specific userexit code around the user or transaction type.
Cheers, Paul.

Inbound IDOC error - GTS

Hi,
We are getting an error while IDOC is posting on to GTS export declaration. (See screen shot of error in the attachment)
The activity referred( ZMXI2) represents the imports, but where as the error we getting is while on export inbound.
Checked all the customization in "Define messages for communication process and Define control settings for Communication process" and every things seems fine.
Please advise on how to correct this error.
Regards
Nag

Hi Nag,
Which fields and values are populated in the iDoc header segment /SAPSLL/E2CCEHD ?
Regards,
Dave

Vendor master changes are dynamically updating in PO

Hi Gurus,
If we are making any changes in the vendor master, this change is immediately available/updating on the existing Purchase Orders like address data and all. How can we avoid this. Client want this changes to reflect only on the new (future) POs after the changes made in the Vendor Master.
I have changed the address details like street name, zipcode and phone number in the vendor master. This changes reflected in the existing (old) Purchase Orders. But the Client don't want the changes reflected on the old POs and these POs should have only the old details.
Greatly appreciated your help on this.
Thanks and regards
Durai

Hi All,
Or how can we check the vendor details with old name that vendor changed the name say one year before.
Thanks and regardd
Durai

ALE IDoc : Vendor Master : Cremas: Inbound IDocs are bypassing the Customiz

Similar Messages

Maybe you are looking for