IDOC for Given Fields

hi all,
is their any IDOC which containes list of below fields
1) Delivery Document Number
2) Document Date
3) Delivery Ship To Number
4) Ship To Name
5) Ship to Address
6) Delivery pertinent text
7) Planned Goods Issue Date
8) Shipment Reference Number
9) Delivery Item
10) Material Number
11) Material Description
12) Unit
13) Serial Number
14) Plant
15) Storage Location
16) Requested delivery date

hi prabhu,
can u map and show me fields with respect to the segments for the above mentioned fields

Similar Messages

Regenerate IDOC for EEWB fields

Hi All
I have added a new field via EEWB and regenerated the IDOC using transaction BDFG (to ensure that the new field appears in the IDOC for population).
In the new message type, I see the additional field added there. I tried testing the IDOC in WE19 by populating the new field - record created but the new field's value doesnt get populated in CRMD_ORDER.
Have I missed a step for mapping - user exit? Please help.. points will be rewarded.
Thanks,
NS

Hi NS,
You need to add XIF site in site admin (SMOEAC).
Then you also need to maintain partner profiles for IDoc exchange. Atleast for this process you need inbound mapping to be defined (WE20).
CRMXIF_ORDER_SAVE should allow you to load business transaction. For the usage, you can refer to txn BDLR where some sample are given for product and partners.
Regards,
Surendar

Trigger IDOC for ADDRESS FIELDS IN DEBMAS06

Hi
i have extended DEBMAS06 and added two new segments:
1) ZE1KNA1M (streetnumber2,3,4,PO_BOX_CTY,PO_BOX_REG
2) ZE1KNVKM.(email and fax from table ADR6 and ADR3 respectively)
now for change in the above fields IDOC has to be triggered using change pointers....may i know how to activate change pointers for these fields?

Hi moorthy,
sending DEBMAS IDOCs via TA BD12 ( Report RBDSEDEB ) will generate an ADRMAS IDOC.
Have a look on the source code - inside FM MASTERIDOC_CREATE_REQ_DEBMAS there is another call of FM MASTERIDOC_CREATE_REQ_ADRMAS.
Regards
REA

Sending idocs for custom field

Hi
I need to send idocs when i save the data in field , the idocs should be send automatically when the data saved to field, please provide the solution.
Thanks
Moderator message: "spec dumping", please work yourself first on your requirement.
Edited by: Thomas Zloch on Jun 23, 2011 9:17 AM

Hi
In case you have created a structure for your custom fields and added it to the standard table then you would be looking for a user exit so that the data entered in those fields from the MM01 or MM02 screen gets stored into the database.
Over there you can trigger a custom event and start your approval workflow.
If the approval is given then set a parameter say Approval as X in the workflow.
Read the workflow container in your exit for this container element and if its value is X,then move the corresponding data to the desired structure or else clear it.
Lets say you have added fields in CJ01 and it has two exits for storing the data in database.PROJ is the table and custom fields added in CI_PROJ
EXIT_SAPLCJWB_002
move-corresponding sap_proj_imp to proj.
EXIT_SAPLCJWB_003 :
call F.M. swe_event create
wait for say a particular time limit after which it should be considered as auto rejected read workflow container for this approval value
if X
move-corresponding proj to cnci_proj_exp.
else.
fire another event to cancel the workflow.
endif.
I am not sure this would be an appropriate way but could be tried.

How to provide F4 help for given field

Hello Experts,
IN moduleprogram screen i have 3 fields .
Plant , material and sorage location.
Based on plant and materil i need to provide the possible values of storage location when we press on F4 on storage location field.
Pleasegive me the code asap.

Hi Raja
Pls go thru the code.
Pls reward pts if help.
Deepanker
REPORT Ztest_HELP .
TABLES : MARA.
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.
PARAMETERS : P_MATNR(10) TYPE C.
SELECTION-SCREEN END OF BLOCK B1.
DATA : BEGIN OF ITAB OCCURS 0,
MATNR TYPE MATNR,
END OF ITAB.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_MATNR.
SELECT MATNR
FROM MARA
INTO TABLE ITAB
UP TO 10 ROWS.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
EXPORTING
RETFIELD = 'MATERIAL NUMBER'
DYNPPROG = SY-REPID
DYNPNR = SY-DYNNR
DYNPROFIELD = 'P_MATNR'
VALUE_ORG = 'S'
TABLES
VALUE_TAB = ITAB
EXCEPTIONS
PARAMETER_ERROR = 1
NO_VALUES_FOUND = 2
OTHERS = 3.
Pls reward pts if help.

Idoc not Trigerring for Change Pointers in CREMAS only for 2 fields

Hi All,
I am trying to trigger the Idoc for 2 fields ( Contact Person First Name & last Name) KNVK-NAMEV and KNVK-NAME1. I have maintained the fields in BD52. Whenever I change the fields, entries get created in CDHDR, CDPOS and BDCP. But the Idloc doesnt get triggerred. But if I change any other fields of LFA1 or LFB1 for the same vendor, the Idoc gets created. Can anybody please help out on this?
Thanks,
Geetha

Hi,
Just check after executing the program "RBDMIDOC" idocs getting triggered or not.
Thanks,
Asit Purbey.

How to find out the description for the given field?

Hi All,
How to find out the description for the given field?
I mean ETTYP Desription is VTEXT. This we can find in TVEPT Table. So, How canwe find this?
Thanks in Advance
Sri...

Hi Avi,
If i want to disply the fields like AUART and 'Description of AUART',
Suppose based on my query i will take AUART from T184 table. And the description of AUART is available in TVAKT table.
my question is if i have given T184-AUART and how do u find out AUART Description ?(How do u know which table is having Description of AUART)?
Thanks in Advance
Sri...

How to split ACC_DOCUMNET03 IDOC after 100 line items for given posting

Hi Friends,
I need to create an IDOC based on the company code and posting date & a particular company code for a given date has reached 100 line items then create another IDOC for that.
EX:
I have 150 Line Items in file
120 Items are related to Company Code "1100" and remaining 30 related to company code "1200"
For this i need to create IDOC's like this
one IDOC with 100 line items which will contain 1100 company code
second IDOC with 20 line items which will contain 1100 company code
Third IDOC with 30 line items which contain 1200 company code
I assume that this can be done through UDF.
Please can you guys help me this.
Thanks in advance.
Thanks,
Vivek.

chk this:
/people/claus.wallacher/blog/2006/06/29/message-splitting-using-the-graphical-mapping-tool

LFA1 Table fields are not updated via IDOC for particular vendors

Hello,
We have a scenario where some of the additional vendor fields in transaction xk02 should be updated via inbound IDOC.
The IDOC segments have the corresponding vendor field values in it.
For particular vendors, the updation is not taking place for those fields.
What could be the possible reason. Kindly help me with this.

Hello,
that may be due to customizing.
You should check with functional consultant.
Regards

I NEED THE TABLE NAME FOR THE FIELD DESCRIPTION GIVEN!

I NEED THE TABLE NAME FOR THE FIELD DESCRIPTION GIVEN!
Partner Type
Partner Type Desc
Partner no
Partner Name
Partner Address 1
Partner Address 2
Partner Address 3
Partner Address 4

Hi Jyotirmoy ,
You can get all partners and their type in table EDPP1, depending of the partner type you need to go to specific table for address and other details, like for partner type KU(customer) goto KNA1,etc for partner type LI(vendor) goto LFA1 etc for partner type B(bank) goto BNKA etc ....
Sirish

Segment for the field EBORT in the Idoc BOMMAT04

Hi Experts,
I want to post the field EBORT(description:Installation Point for Subitem) through
the Idoc BOMMAT04 so please may I know the segment in this Idoc for this particular feild.
Regards,
Kiran.

Hi,
the field EBORT is in the chile segment
<b>E1STPUM Master BOM sub-item</b>
You yourself can search in WE30 entering the IDOC name type
regards,
nazeer

Batch Number field in IDoc for Process Orders (message type LOIPRO01)

Hello PP experts,
Just wanted to ask if anyone of you have worked with message type LOIPRO01 (IDoc for process orders)
There is a segment-field in this IDoc E1RESBL-CHARG which has description of "Batch Number"
We tried to assign a Bath Number for an Order (using t-code COR2 --> "Goods Recpt" tab under "Receipt" section), generated an IDoc for this order, but upon checking the E1RESBL-CHARG field of the IDoc it is not populated with the Batch Number.
The material in the process order is FERT, so technically we're trying to assign a Batch Number in one of the process orders for a Finished Goods material type, so not on the component level.
Can anyone here verify:
1. is the E1RESBL-CHARG field of IDoc LOIPRO01 intended for the Product Batch Number? If Yes, how do we populate that for in the IDoc? --> Do I need to have a Reservation/Dependent Requirement for the Product for the Batch Number to be populated in the IDoc?
2. If E1RESBL-CHARG can not be populated for a Product that has no Reservation/Dependent Requirements, Do I have any option of populating this field with just the Batch Number assigned to the Process Order of that product?

Solved - LOIPRO01 IDoc does not pick up the Batch Number from AFPO table, instead from table RESB. We need batch from AFPO and just created a lookup using the Process Order Number as import param

Mass maintainenance of material master for the field MARC-NCOST,SOBSK

Hi
While maintaining two fields NCOST and SOBSK for hude materials using MM17 transaction, the transaction executed properly while saving the transaction. There is no warning and error messages for all materials. But it was not updated in material master or in tables. for other field relavent to MRP updated correctly.
when I am maintaining manually for each material it is taking the value update the same.
Please explain the problem why it was not updating and let me know the solution.
Regards
Kishore

Hi,
Thanks for ur response.
I am getting green light. Please note the application message given below.
"The material cannot be maintained since no maintainable data transferred
Message no. MG160
Diagnosis
You wanted to maintain an existing material master record as follows:
By changing it
However, you have not yet maintained the material master record for the organizational levels and data fields specified, or user departments selected. You can therefore process this data only in Create mode.
By extending it
However, you have already fully created the material master record for the organizational levels and data fields specified, or user departments selected. You can therefore process this data only in Change mode.
In both cases, this message can appear if there is no maintainable user department left. This occurs if you have not set the Check required fields indicator when transferring data (program RMDATIND). Although the absence of an entry in required fields does not then necessarily result in an error, the number of maintainable user departments is reduced accordingly.
Procedure
Depending on the cause, maintain the material master record in Create or Change mode, or also transfer the missing required fields."
where can I find IDoc list for this transaction.
Regards
Kishore

Correlation for multiple fields in messages inside BPM

Hi All,
We have a requirement to collect multiple IDOCs based on combination of field1,field2,field3 and field4.
Could you please tel me possible ways to implement this solution:
I have tried the below options:
Multiple fields in one correlation
Correlation name is given and then in Correlation editor,we have given all four fields in correlation container and 1 involved message and properties are given for all fields
Using this solution.IDOCSa re not collected even if all the IDOCs coming with same value for (field1field2field3+field4)
for example even if combination of (field1field2field3+field4) is same still its not collecting and sending each IDOC sepearately outside BPM.
Could you please suggest where the problem is?
Please suggest if there is any other way to implement this in BPM.
Thanks in advance
Best Regards,
Harleen Kaur Chadha

Hi Harleen Kaur Chadha,
Open your Integration Process (ccBPM), go menu bar u201CViewu201D, select u201CCorrelation Editoru201D. Then you can see the Correlation variables you have declared. Go the third tab u201CPropertiesu201D, and then try to edit u201CValueu201D. Expression Editor window pops up, select u201CInterface Variableu201D, then select XPath. Now edit u201CXPath Expressionu201D. Pay attention to Prefix u201Cp1u201D, it should be present in XPath expression. Check SAP help [Link|http://help.sap.com/saphelp_nwpi711/helpdata/en/3c/831620a4f1044dba38b370f77835cc/frameset.htm]
Regards,
Raghu_Vamsee

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

IDOC for Given Fields

Similar Messages

Maybe you are looking for