Validation on outbound idoc

Hello team
I have the below requirement now. please check and suggest me
1. i am sending outbound MATMAS05 idoc from SAP system. but i want to do few validations on the data of idoc (for example i will check the value of plant data with some other value of the table). if my checking is success then only i need to create outbound idoc and send it to downstream systems.
So now i want to know where i need to write the code which performs the validations against the data before creating/posting of idoc.
Please suggest me.
Regards
Raj

Vinod
Dont mine of asking little more clarification. you mean to say go MM01 and find out the package (ie MGA) and then goto SMOD and findout the exits right.
But when check in this way, i didnt find the enhancment MGV00001 you have provided.
please tell me the procedure to check in a detail way. i want to know how can we check for the related enhancments for any idoc type. please tell me to check for MATMAS05 as an example, i will use the same techinque for any idoc type.
Regards
Raj

Similar Messages

Procedure to Error Out Outbound IDocs

Hello,
 I have a Requirement in which I am using ORDERS05 IDoc Type and extended it to ZORDER05 to populate Custom Fields and sending the Purchase Order Outbound IDoc to the Vendor from SAP System. Now, my requirement is that if any of the Custom Fields are not maintained in SAP and not populated in the IDoc, I need to Error Out the IDoc with Error Status 26. I am currently working on the SAP ECC 5.0. I have implemented similar Error Handling Mechanism earlier by using Enhancement Framework as I was working in ECC 6.0 environment where I've added the Code by Creating an Enhancement Implementation in the Function Module IDOC_CREATE_ON_DATABASE. But since ECC 5.0 does not have the Enhancement Framework feature, please let me know how to achieve this.
Thank You,
Venkata Phani Prasad K

Hi
why don't you try using the standard method for validation of data?
By implementing the customer-function EXIT_SAPLEINM_002 or BAdI MM_EDI_ORDERS_OUT you can make checks of completeness of the idoc segments (in your case, additional custom data) and, if they were not complete, report an error message raising the exception DATA_NOT_RELEVANT_FOR_SENDING
ie
if <Idoc Custom Field> is initial.
MESSAGE ID 'S1'
 TYPE 'E'
 NUMBER '333'
 WITH Additional data are incomplete'
 RAISING data_not_relevant_for_sending.
endif.
Thus you have the evidence of the error in the processing log of the output message while the IDOC is not created.
The solution works very well and is not invasive.
Regards.
Andrea

Attaching Error Status to Outbound IDOC. ?

Hello Experts,
We have a scenario in SAP PI / XI were upon creation of a Sales Order , Purchase Order or Material Master Flow to Non-SAP System through SAP PI/XI , the IDOC shouldn't flow to SAP PI following a validation on Material Group.
The IDOC is triggered through Output Type , there is a custom Z function module which create outbound communication IDOC. This output type is attached to a Process Code ZSO, ZMPO defined for respective scenarios defined above.
Currently i am attaching the the status = 07 to control data structure & the IDOC is getting created but is having error.
Is this the right practice to follow for attaching error message Outbound IDOC.
Awaiting for your response.
Best Regards
Priyesh Shah

It depends on the business requirement.
in a previous project, if there was any error during the validation of the data within the iDoc before it is created and sent, i would trigger an error and send the error to the person who created the data with the error for them to correct. they would then correct the error within the document and save and the iDoc would be triggered and sent correctly.

Outbound Idoc through Workflow in CRM

Hello,
Consider this scenario, I need to create an opportunity document through Idoc inbound in CRM 4.0. There are certain validations done at the XIF layers as well as the application layer.
In case if there are any errors in the Idoc or errors the opportunity document created(application level errors), I need to send an outbound Idoc containing complete inbound Idoc data with certain rejection codes.
Can some body let me know the best way to achieve this. I
If this can be achieved through workflow, please provide the complete details on how to go about this.
Thanks In Advance,
Kiran

Hello,
Consider this scenario, I need to create an opportunity document through Idoc inbound in CRM 4.0. There are certain validations done at the XIF layers as well as the application layer.
In case if there are any errors in the Idoc or errors the opportunity document created(application level errors), I need to send an outbound Idoc containing complete inbound Idoc data with certain rejection codes.
Can some body let me know the best way to achieve this. I
If this can be achieved through workflow, please provide the complete details on how to go about this.
Thanks In Advance,
Kiran

Query on User exit for outbound idoc

Hi ,
Can u all pls help me out to solve these queries
1. when we extend a new segment (at we31) and create a new idoc type(at we30), say,for DELVRY05 idoc type-what is the logic to be written inside the Exit(at Transaction code - CMOD -where a project is created and the exit is found for the enhancement) ,to view our extended segment -that needs to be appended (viewed below the existing segment)at we02?
2.Can we delete the outbound idoc generated with errors from development server?
3.How to recify the outbound idoc errors-like runtime,syntax,port unreachable errors(at the status record and data records listed inside we02 transaction code)?
4.How to check values populated at our extended segment inside we02-Transaction code.
say,the logic required inside the exit may be,
Select single ladel from eikp into wa_ladel where refnr = (inbound delivery)
In this,the ladel exists in eikp table as EIKP-LADEL field.
The main thing is- an inbound delivery is created at transaction code VL31N for which an outbound idoc(using an Exit )should be generated with few more validations for the fields like
i) ekpo-pstyp(corresponding IDOC segments are E1EDL26-PSTYV )
ii)ekko-lifnr and ekko-lichn(E1EDL24-LICHN )
Segment name-item(at transaction we63) Segment no.
iii) E1TXTP8-TDLINE => SCAC Code. 11
 E1TXTH8-TDID => Z001. 10
iv) E1TXTP8- TDLINE => Primary seal number. 13
 E1TXTH8-TDID => Z002. 12
v) E1TXTP8- TDLINE => Secondary seal number. 15
 E1TXTH8-TDID => Z003. 14
5.Can you help me out to know the logic by which we can validate few fields from different tables like eikp,ekpo and ekko inside our Exit (in the project created at CMOD transaction?
With Regards,
Srividya

Hi Swati Choudhary,
please ask your question in devlopment forum, please see its 2 yr old thread, and i don;t think Phileas Fogg still remember his stuffs.

About Orders05 outbound Idoc.

Hi,
I am using an outbound idoc of basic type Orders05 with an extension of the idoc header segment.This outbound idoc will get triggered once a PO is saved and sent through EDI.
I have to do an enhancement wherein I have to populate the mode of transport field(EXPVZ) and place of loading(LADEL) in the fields of the extended segment selecting them from EIKP depending upon the BELNR value in the header of the idoc(E1EDK01-BELNR).
I am unable to understand how do I populate the fields.
Could you please help me.
Thanks,
Sandeep.

HI,
see the below steps you will completely understand the processing outbound..
2.1 Outbound Interface
PROCESS DIAGRAM
Outbound Interface
1. Analyse Hierarchy Levels
2. Create New segment
3. Create New IDoc Type
4. Create New Message Type
5. Link Message with IDoc Type
6. Create an entry in EDP13 via transactions WE20 and BD64
7. Populate the Custom IDoc via ABAP Program
7b Error Handling
7c. Send Status Email
8. Test the Population of the Custom IDoc
Step 1 Analyse Hierarchy Levels:
Analyse the data relationships being processed in the interface. Define the appropriate hierarchical Parent-to-Child relationships.
Navigate to transaction code WEDI
Transaction WEDI displays the IDOC main menu. This allows navigation around the various development and control areas to create a customised IDOC.
Step 2 Create a new segment:
via wedi : Development - IDOC Segments or Transaction code WE31.
 Enter segment name and click on Create.
 The name of the segment type must start with Z1 , and have a maximum of eight characters.
 Enter description and enter the relevant field names and data elements.
 The segment should represent a structure in the program so for each field in the segment a field name and a data element must be defined.
 Save the segment and enter Person Responsible and Processing Person .
 Go to Edit and Set Release.
 Repeat this procedure for each new Segment in the IDOC.
Step 3 Create a new IDOC Type
via wedi Development - IDOC Types or Transaction WE30.
 Enter segment name (starting with Z), click on Basic Type and then Create.
 Create as new, enter Person Responsible and Processing Person and enter description.
 On Create Basic Type screen decide where segments should be inserted and go to Edit/Create Segment.
 Complete relevant fields in the Maintain Attributes screen:
 From the relevant segments created in Step 2 enter the Segment type and if mandatory segment.
 The Minimum and Maximum number of segments to be allowed in the sequence. (One minimum and one maximum if segment is mandatory).
 The Parent Segment and Hierarchy Level will be automatically created depending on where in the IDOC tree you decided to create that particular segment.
 Repeat this process for each segment needed in the IDOC type, deciding whether to add the next segments at the same level or as a Child.
 When IDOC created return to initial screen. Go to Edit and Set Release.
 Go to Transaction WE60 to view the IDoc Type you have created.
Step 4 Create new Message Type
via wedi Development - Message Types or Transaction WE81.
 Display/Change and click on New Entries
 Create a new Message Type and Save.
Step 5 Link Message Type to IDOC Type
via wedi Development - IDOC Type/Message or Transaction WE82.
 Display/Change and then click on New Entries.
 Enter Message Type, Basic Type (IDOC Type) and Release (46C) and Save.
Step 6 Create an entry in EDP13 via transactions WE20 and BD64.
The partner profile for the Idoc must be set up and generated in the transaction BD64 and transaction WE20.
 WE20 Add Message Type to appropriate Partner Type, Enter Message Type, Receiver Port and Idoc Type and Save.
 BD64 Create a Model View, Enter Sender and Receiver Ports, Attach Message Type. Go to Environment on Menu and click on Generate Partner Profiles and generate (not save) profile.
Step 7 Populate the custom IDOC via ABAP Program
See Test Program ZOUTBD_IDOC_TEMPLATE, Appendix IV.
 Create an Internal Table for each segment type, this should be exactly the same structure as the segment type.
 The control record is filled into a structure like EDIDC. The message type and the Idoc type for the Idoc must be populated into the eddic structure.
- PERFORM populate_Control_structure USING c_mestyp
 c_SEGMENT_type1.
 The data segments are filled into a structure like edidd-sdata; sdata and the segment name are populated into the edidd structure.
- PERFORM transfer_Parent_data_to_seg.
 The standard SAP function module MASTER_IDOC_DISTRIBUTE is called to pass the populated IDOC to the ALE Layer.
- PERFORM master_idoc_distribute.
 NOTE: This function module is only called for stand alone programs and Shared Master Data programs (SMD). It is not called when using extensions or output determination.
 The ALE Layer handles the sending of the IDOC to the receiving system.
 Error Handling (see Step 7b).
 Commit work.
Project Specific
Step 7b Error Handling Analyse which fields in the interface are mandatory for the receiving system and who needs to receive error notification.
 Declare a structure of type MCMAILOBJ for sending instructions.
 Enter values for the internal table based on structure MCMAILOBJ
 For selection processes, on SY-SUBRC checks and where fields are mandatory for the receiving system; insert Function Module MC_SEND_MAIL.
 Enter values in the following parameters: -
MS_MAIL_SENDMODE = B (Batch Mode)
MS_MAIL_TITLE = 'Mail Title'
MS_MAIL_DESCRIPTION = Error description (e.g. MATNR not given)
MS_MAIL_RECEIVER = Name of Receiver (To be determined)
MS_MAIL_EXPRESS = E (Express Delivery)
MS_MAIL_DLINAME = Leave Blank
MS_MAIL_LANGU = 'E' (Language)
MS_MAIL_FUNKOBJ_NAME = Leave Blank
TABLES
 MS_MAIL_CONT = I_MCMAILOBJ
Note:
It has to be determined separately for each interface how these errors and mail notifications are to be grouped dependant upon the number of errors that are potentially likely. One possible approach is to send an email for each reason for rejection and include all the records that failed for that reason in the mail notification. Another possible approach is to send an email for every failure.
When error checking for mandatory fields it is common SAP practice to reject a record on its first failure (irrespective of subsequent errors in that record)
Step 7c Send status mail
 Append to table I_MCMAILOBJ details of the time the interface was processed, how many Idocs were created and how many of these produced a status of 03.
 Select the user to receive the mail from ZINT_RECEIVER, using the name of the program as a key (SY-CPROG).
 Use function Module MC_SEND_MAIL to send a mail to the user containing the contents of I_MCMAILOBJ at the end of the interface processing.
Step 8 Test the population of the custom IDOC
via wedi IDoc - Display IDoc or Transaction WE02.
 Enter your message type and execute.
 Status should be green, double click on one of the Idocs you have created to view its contents.
 If a problem has occurred click on Status which will give you a description of the error.
 Drop down Data Records arrow and this should list the data in the IDoc in the correct hierarchical structure.
 Click on each individual segment and view the content to check that the correct data has been read.
 If you have UNIX access by using AL11 you can view the file that you have created.
Note:
For some interfaces it may be valid to send an empty file to SAP. This empty file is converted to the custom IDOC format expected by SAP. This custom IDOC will contain dummy information. In the inbound processing code, if the dummy information is identified then the processing of the IDOC is considered to be complete and the IDOC should then be assigned a successfully processed status of 53, even though it has not been processed at all.
rewards if useful
regards,
nazeer

Why does an Inbound IDoc no change and differs from an Outbound IDoc no?

Hi Experts,
This seems to be a basic question..! But can someone kindly clarify why an IDoc number gets changed when sent from one R/3 system to another R/3 system and how does this happen???
i.e., whenever an IDoc was triggered from R/3 system A to R/3 system B through XI/PI, the Inbound IDoc number (in system B) differs from the Outbound IDoc number (in system A)... Why does this happen and how???
Thanks in advance!
Br,
G@nesh

Hi Ganesh,
The IDOC numbers are always Unique,
IDOC can be generated in SAP system as a result of internal testing (WE19), or
can be posted from a non sap system (say PI).
So every time a new IDOC comes, it is assigned a new number to avoid confusion and also this plays a
critical role in the end to end testing and validation.
If you look at the control record of the IDOC you can see a element called DOCNUM. this stores to actual IDOC number.
from PI side you can use IDX5 and in ECC We02/05 to notice the idoc numbers.
Regards,
Srinivas

BADI for PO OUTBOUND IDOC

Hello Experts,
Please help me out finding a suitable BADI for T code: ME21N
OUTBOUND IDOC.
Scenario:
I have to populate a "Z" segment while creating an IDOC in ME21N. for this I require a BADI.
I have tried using FM: idoc_output_orders
Form Routine fuellen_idoc_inttab.
but ME21N doesn't execute it at all !!!
I have set my Output Type to EDI with the Valid Settings
when ever i create a PO it creates an IDOC but it doesn't execute FM idoc_output_orders
Thanks in Advance!!!
R

Hi,
Below steps for your reference.
1.M/59 Define Condition Tables
2.M/50 Define Access Sequences
3.NACT Define Message Types
4.Set up fine-tuned control for each message type
5. NACZ Define Message determination shemas
6.NACR Define Condition Records
Regards.
David.

Steps for creating a custom outbound idoc

Hi,
Can u please each and every step wise for the creation of the custom outbound idoc.
Thanks
Kiran Prasad.

friend before posting ur query, try to utilize the search tab in the forum, u can find the answer for ur query if not continue with postings.
Follow this link for step by step tutorial with screen shots
http://www.****************/Tutorials/ALE/ALEMainPage.htm
1. Create an IDOC Type.
The next step is to create an IDOC type by associating the extension type that you created with the Basic IDOC type. This is a simple process:
u2022 From transaction WE30 or WEDI go to Development -> IDOC Types.
u2022 Enter ZDEBMASZ for Object Name.
u2022 Click on IDOC Type.
u2022 Click on Create.
u2022 Enter DEBMAS02 for Basic IDOC type.
u2022 Enter ZDEBMASX for extension type.
u2022 Enter a description.
u2022 Enter.
u2022 You will see a display of the composite IDOC type with all segments, including Z1SADRX (see Figure 3).
It is possible to associate only one extension type with a Basic IDOC type for a given IDOC type. However, you can have multiple new segments in an extension type.
2. Link IDOC Type to Message Type.
The next step is to link the new IDOC type to its corresponding message type. This is important, because this relationship is referenced in the partner profile parameters where you specify the message type and IDOC type to be used for that particular representative system. To link the message type:
u2022 Use transaction WE82, or from WE30, go to Environment -> IDOC Type / Message Type, or from WEDI go to Development -> IDOC Type -> Environment Î IDOC Type / Message Type.
u2022 Click on Display <-> Change.
u2022 Click on New Entries.
u2022 Enter DEBMAS for message type.
u2022 Enter DEBMAS02 for Basic IDOC type.
u2022 Enter ZDEBMASX for extension type.
u2022 Enter your SAP R/3 release number for Release.
u2022 Save.
This data is stored on the EDIMSG table and is accessed by several ALE processes to relate the message type to the IDOC type.
3. Check the IDOC Type.
Before checking the IDOC type for consistency, it is important to perform another step that releases the extension type to the IDOC type:
u2022 From WEDI go to Development -> IDOC Types -> Extras -> Release Type, or from transaction WE30 go to Extras -> Release Type.
u2022 For the Object Name ZDEBMASX and radio button Extension Type, click Yes.
u2022 The extension type has now been "released."
You canât edit the extension type once itâs released. To cancel the release for further editing or deactivation, go to WE30 Î Extras Î Cancel release. The final step in the IDOC extension process is checking the validity of the IDOC type:
u2022 From transaction WE30 or WEDI go to Development -> IDOC types.
u2022 Enter ZDEBMASX for Object name.
u2022 Click on Extension Type.
u2022 From the Development Object menu select Check.
u2022 Repeat the operation for IDOC type ZDEBMASZ.

Outbound IDOC process - Using standard or Custom Program

Hi all,
i'm having some doubts regarding IDOC's outbound processing.
I'm trying to understand 2 scenarios:
1- Trigger Standard Outbound IDOC without writting any Z program ou IDOC FM.
It's possible to trigger a outbound idoc for exemple, whenever a sales order is created. To do this is, i suposed i don't need to write any code at all, correct?
What i need to do is create a logical system (SALE), define Transmission protocol (WE20, in here i associate the partner, and the outbound message type? After this point is the idoc automatic triggered?
If not, what is the correct procedure?
2 Trigger Ountbound IDOC using Z program.
Whats is diferent from the point 1 to this situation?
Best regards,
Pedro

Kali,
1. You can search in SE37 using IDOC_OUTPUT* for finding out corresponding function modules. It is based on message types.
2. You can search user exit in above mentioned function module. So first get the correct populating FM & then you can search for Call Customer Function inside the code for user exit.
3.Again ans is same as in point 1.

Is it possible to generate outbound idocs for FI invoices? How?

Is it possible to generate Outbound idocs for FI invoices? How? or else i have to write program to get data in file and pass it to translator. Please help.

Dear Gabriel
Before letting you know the possibility, can you please let me know why you want such a requirement, since standard has not provided such copy control, to my knowledge.
As you would know order type KB is for consignment fillup where you are just transferring the goods from FG unrestricted to your own warehouse and that is why in standard you can see the copy control KB --> F8 which means you can raise proforma against delivery and not against fillup order.
So think of whether really you wanted to raise proforma against fillup order which is NOT recommended by SAP. However, still if you feel that the requirement is so to have, you can make the settings in VTFA.
thanks
G. Lakshmipathi

Function Module to Generate Outbound IDOC for Sales Documents

Hello Experts,
Can someone please help me, I need to know which function module to use in order to generate the outbound IDOC for sales documents. Some of the fm's I have come across are the following:
IDOC_OUTPUT_ORDERS, but actually for Purchase Orders
IDOC_OUTPUT_ORDRSP, but did not generate any IDocs for my sample Sales Order.
Points will be given for any help provided.
Thanks in advance.

Hi Nagaraj,
I tried using the IDOC_OUTPUT_ORDERS but I keep getting an error that the Purchase Order <xxx> does not exist, even though the document I tried is a sales order. For everyone's reference here is the code:
form process_data.
DATA v_idoc TYPE edidc-docnum.
DATA i_edidd TYPE TABLE OF edidd.
DATA wa_idoc_ctrl TYPE edidc.
LOOP AT i_nast INTO wa_nast.
 CLEAR i_msgs[].
 CALL FUNCTION 'WFMC_PROTOCOL_GET'
 EXPORTING
 cps_nast = wa_nast
 tables
 messages = i_msgs
 EXCEPTIONS
 NOT_FOUND = 1
 OTHERS = 2.
 LOOP AT i_msgs INTO wa_msgs WHERE arbgb EQ 'E0'.
*--- Check first if there is an IDOC
 IF wa_msgs-msgv1 IS INITIAL.
 CONTINUE.
 ENDIF.
 v_idoc = wa_msgs-msgv1.
 CLEAR i_edidd[].
 CLEAR wa_idoc_ctrl.
 CALL FUNCTION 'IDOC_READ_COMPLETELY'
 EXPORTING
 document_number = v_idoc
 IMPORTING
 IDOC_CONTROL = wa_idoc_ctrl
* NUMBER_OF_DATA_RECORDS =
* NUMBER_OF_STATUS_RECORDS =
 TABLES
* INT_EDIDS =
 INT_EDIDD = i_edidd
 EXCEPTIONS
* DOCUMENT_NOT_EXIST = 1
* DOCUMENT_NUMBER_INVALID = 2
 OTHERS = 3.
 CALL FUNCTION 'IDOC_OUTPUT_ORDERS'
 EXPORTING
 object = wa_nast
 control_record_in = wa_idoc_ctrl
* IMPORTING
* OBJECT_TYPE =
* CONTROL_RECORD_OUT =
 tables
 int_edidd = i_edidd
* EXCEPTIONS
* ERROR_MESSAGE_RECEIVED = 1
* DATA_NOT_RELEVANT_FOR_SENDING = 2
* OTHERS = 3
 IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 ENDIF.
 COMMIT WORK.
 ENDLOOP.
ENDLOOP.

Automated error email notification when outbound IDOC fails

Hi,
The requirement is that whenever the outbound IDOC of message type PAYEXT, basic type PEXR2002, fails, then email has to be trigerred to a group id.
I had suggested to write a report program that runs as a job. If the IDOC goes to error status then mail will be sent from this report. Client prefers it to be done through workflow.
There is a standard process code for outbound IDOC failure handling EDIO (we40). standard task 7989 has been assigned to this process code. I dont want to modify this standard task as I am not sure of impact.
Terminating event for this task is 'ERRORPROCESSCOMPLETD'.
I have developed the workflow that has trigerring event 'ERRORPROCESSCOMPLETD' and bound with the IDOC number. This will send mail to the group id with the IDOC details
Now issue is that, I am not sure if standard process EDIO will be trigerred automatically, or should we configure anywhere. Since this is standard outbound IDOC, I am not able to add the process code in partner profile.
Please give your inputs or any other alternate solution to send mail through workflow when outbound IDOC fails.
Thanks in advance.

Hi,
I guess in your outbound partner profile for PAYEXT. you need to add process code EDIO in message control TAb. WHich will cause to trigger the workflow which will send the notification.

Outbound IDOC WPDTAX not getting generated

Hi
I am not able to generate outbound IDOC WPDTAX through WPMA transaction.
We are using TAXUSJ as the tax procedure.
Tax Condition type UTXJ and JR1 has been maintained in the system.
On looking at the code against WPMA ,
POS_TAX_GET is called to calculate taxes.
It does not have a fetch against all the condtion tables for tax.
The above condition has been maintained in table A053.While the above program fetches data against only A003.
Can somebody help?
Regards,
Amit.

Hi Amit,
For TAXUSJ, the conditions maintained are time dependent conditions.
However , IDoc type WPDTAX01 does not support time dependent conditions.
Only time independent conditions will be transferred with the help of Idoc type WPDTAX01.
http://help.sap.com/erp2005_ehp_03/helpdata/EN/3f/81e33bfa5d11d38d1f080009d10d9a/frameset.htm
Regards,
Lisa

Message type for Scheduling Agreement - Outbound IDoc

Hi All,
I have to create an Idoc for Scheduling Agreement through a Z program based on some conditions. I have bit confusion, whether i can use Idoc type for Orders(e.g ORDERS01..05) & Message type ORDERS / ORDCHG to generate Outbound Idoc.
Already there is process code for for ORDCHG mappig IDOC_OUTPUT_ORDCHG & ORDERS mappig IDOC_OUTPUT_ORDERS. Whether there will be any impact on this.
Appreciate your help.
Regards,
Anbalagan.

Hi Anji,
Thanks for the Reply. But i think ORDRSP is for Order Confirmations.
But I have to send Outbound Idoc for a Schedule Agreement.
Whether the same Idoc type & Messge type used for SO/PO(e.g ORDERS05, ORDERS/ORDCHG) can be used for Scheduling Agreement.
Please Advice.
Regards,
Anbalagan

Validation on outbound idoc

Similar Messages

Maybe you are looking for