Basic type DELVRY03 and FM IDOC_INPUT_DELVRY

Hi experts,
i have a prblem using the basic type DELVRY03 and FM IDOC_INPUT_DELVRY. on transaction we19 am passing data to the segments of the basic type delvry03 so that i can update an outbound delivery...the problem here is that when am running the FM idoc_input_delvry....the data for the first item are updated correctly, but the second item is not updated properly...for the second item, the picked quanity is not taken from the segment E1EDL24...instead, this value is added to the delivery quantity...
for example if the delivery quantity is initially 80 for the second item and in the segment e1edl24 i supply 80 to the field LGMNG...this value is not taken as the picked quantity but added to the delivery quantity and hence i get the delivery quantity as 160 and picked quantity as 0....
I kindly requset you to please help on this...
Points will be rewarded...
Thanks,
Vitish.

Hi vitish,
Please check whether u have given right batch number in the CHARG field..if no batch is there then u should not give any batch number...
Regards,
Madan Gopal Sharma

Similar Messages

Inbound idoc mess type:DESADV basic type: DELVRY03 Item text

Hi all,
W're having a inbound process to create inbound deliveries via IDOC.
mess type:DESADV basic type: DELVRY03
We want to create a item text on the delivery via the IDOC. Is this possible?
I see that there's a segment E1TXTH9 - E1TXTP9 to put in texts.
But as I see it, to create a text, we have to give the delivery nr in TDOBJECT TDOBNAME TDID TDSPRAS LANGUA_ISO.
But since we are creating it, this is not possible.
Is there any way to create an item text on an inbound delivery via the IDOC? And how.
Thanks a lot!
Caroline,

Hi Chris,
Before end of the ur functiond module (Idoc_input_xxxxxxx) create an Enhnacement spot . at this point I hope so delivey will be created already .so now u can get the delivery number
**********The Logic for Text Field filling*******************
IF NOT vbeln IS INITIAL.
DATA : L_FNAME TYPE THEAD-TDNAME,
 L_FID TYPE THEAD-TDID,
 IT_TLINE TYPE TABLE OF TLINE,
 WA_TLINE LIKE LINE OF IT_TLINE.
CONSTANTS :C_FID TYPE THEAD-TDID VALUE '0004',
 C_FID1 TYPE THEAD-TDID VALUE '0007',
 c_Text(40) type c value 'xxxxxxxxx',
 C_LANG TYPE THEAD-TDSPRAS value 'E',
 C_FOBJECT TYPE THEAD-TDOBJECT VALUE 'BELEG',
 C_FFORMAT TYPE TLINE-TDFORMAT VALUE '*'.
Reading the Idoc data table for Text field population
 READ TABLE IDOC_dATA INTO IS_EDIDD
 WITH KEY SEGNAM = c_segnam_e1edkt2.
 MOVE IS_EDIDD-SDATA TO IS_E1EDKT2.
 CONCATENATE mrm_RBKPV-BUKRS mrm_BELNR mrm_GJAHR INTO L_FNAME.
 if sy-subrc = 0.
 MOVE: IS_E1EDKT2-TDLINE TO WA_TLINE-TDLINE,
 C_FFORMAT TO WA_TLINE-TDFORMAT.
 APPEND WA_TLINE TO IT_TLINE.
 CALL FUNCTION 'CREATE_TEXT'
 EXPORTING
 fid = c_FID
 flanguage = C_LANG
 fname = L_FNAME
 fobject = C_FOBJECT
 SAVE_DIRECT = C_X
 FFORMAT = C_FFORMAT
 tables
 flines = IT_TLINE
 EXCEPTIONS
 NO_INIT = 1
 NO_SAVE = 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.
I hope it resolves ur problem.Please let me know if u have any
Queries.
Rgds
Sree m

Testing IDOC basic type DELVRY03

Hi,
Can anyone tell me how can i test DELVRY03 idoc for ASN. The Idoc is not being triggered from any document as the data is coming from external system to the Ztable and I don't know how IDOC should be triggered.
Function module is Z_ZZ_IDOC_OUTPUT_DELVRY.
Message Type DESADV.
Can anyone tell me in this scenario until the desicion is made for triggering option, can i test the IDOC somehow.
Regards
Rinku

Hi Rinku,
Could you please clear about your requirement?
If you want to re-test a idoc, use tcode WE19. Input idoc number and execute. Then in the next screen click on the "inbound function module" button, enter the inbound function module and select the radio button process in foreground.
Thnaks & Regards
Vijayanand

LSMW with IDOC Message type COND_A and Basic type COND_A01

Hi Sap All.
in my project we using the LSMW with IDOC Message type COND_A and Basic type COND_A01 and now the requirement is to know the list of the tables which will be updated when i do the LSMW Migration with this IDOC Basic type.
i have tried to know the list of the tables updated by entering into the transaction we30 and looking at the segments E1KOMG,E1KONH, E1KONP,E1KONM,E1KONW and i found that the following below are the list of tables which gets updated when i populate the data into IDOC Message type COND_A and Basic type COND_A01.
KOMG,KONH,KONP,KONM,KONW.
please correct me if iam wrong.
regards.
Varma

Hi Varma,
The tables mentioned by you definitely get updated, i guess you can add KONV to the list too, but to be a 100% sure, enable SQL trace and process an IDOC. Then you can look for Insert/Modify/Update statements to get a list of the tables that get updated.
Regards,
Chen

How to populate custom fields in SAP standard Basic type DELFOR01(E1EDK09)

I've a requirement to include and populate 2 custom fields in SAP standard basic type DELFOR01 and Segment E1EDK09 (it is at hierarchy level 1 ) .
The requirement looks very simple but for this, as per my knowledge, I have to create a new Basic type with the copy of segment E1EDK09 and attach it to outbound process code and write my own function module to populate the segments.
It seems ok but the there are some existing codes in the user-exits for the SAP standard function module.These codes will not get triggered.(Or I've copy the user-exits code in my FM)
Can we do it any other way to handle this kind of situation?
Thanks in advance for your suggestions and help.

Hi Phani,
You have done it correctly. ECC additional data to be moved to EWM, 1. you need to enhance the CIF for master data/ bapi to populate the data in the custom field in EWM. 2. Make your your are not enhancing only one structure. You need to do it in the CI includes so that the field is available in all the related tables/structures.
3. The BAPI/FM which updated these tables will take care automatically to update the custom field data if the field is correctly added in all the tables.
4. If the custom fields are added correctly and still the data is not getting saved , then need to check the mapping of the custom field and bepi extension.
Let me know if this helps.

LSMW Upload SalesOrder Creation:problem in assigning Partner type SH and SP

Hi
I'm trying to upload sales order creation data using LSMW -BAPI Method
Business Object : BUS2032
Method : CREATEFROMDAT2
Message type : SALESORDER_CREATEFROMDAT2
Basic Type : SALESORDER_CREATEFROMDAT202
and I'm passing the following header data
Sales Order Type, Sales organisation, Distribution Channel, Division, Sold To Party, Ship To party,
Purchase order number, PO Date, Requested delivery date, Order Reason, Payment terms, Incoterms part1, Incoterms part2, Document Currency.
and the following item data
MATERIAL NUMBER
Order quantity
Storage Location
Item Category
Item Usage
Reason for Rejection
Plant
Net Weight
Gross Weight
Condition Type
Amount
Internal Order Number
I'm assigning the header data to structure E1BPSDHD1
and Item data to E1BPSDITM,E1BPSDITM1
and Partner data to structure E1BPPARNR.
When I am assigning Partner data to the structure E1BPPARNR, I want to assign both sold-to-party and ship-to-party ,(because I have two source fields of this type) but there is only target field related to the partner data , here I am assigning partner type as SP and partner number as sold-to-party, still there is an unassigned field ship-to-party, for this field I am unable to find a relevant target field so please help me how can I assing These two flat file fields (sold-to-party,ship-to-party)
Looking for further more information : if there is many sold-to-party's and many ship-to-party's how can I go that in this situation i.e maintaining Many to Many relationship using LSMW tool
Thanks in advance
regards
Rajasekhar

Here is what you have to do.
In field mapping, double click on the field PARTN_NUMB (or any field of that structure) in change mode. This opens up the code editor. There just enter the following code. I am assuming you are doing only these fields. But if you are mapping more fields of this structure, you have to map them here.
E1BPPARNR-PARTN_NUMB = ORDERHEADER-KUNAG.
E1BPPARNR-PARTN_ROLE = 'AG'.
E1BPPARNR-ITM_NUMBER = '000000'.
*-- add more field mappings here, if needed
TRANSFER_RECORD.
*-- Now pass the Ship-to record
E1BPPARNR-PARTN_NUMB = ORDERHEADER-KUNWE.
E1BPPARNR-PARTN_ROLE = 'WE'.
E1BPPARNR-ITM_NUMBER = '000000'.
*-- Add more partners if needed by copying the above code.
Remember, you need to do TRANSFER_RECORD only that many times as you have the partners. There will be one 'TRANSFER_RECORD' at the end of this structure, so keep that in mind.
Srinivas

F110S - debugging - Idoc basic type PEXR2002

Hi,
i'm trying to debug F110S and its not stopping in FEDI0003 routines. am i missing something.
i have to populate bank details in this Idoc (basic type pexr2002 and message type PAYEXT)
please let me know.
Thanks.
Edited by: vij k on Aug 5, 2009 9:51 PM

figured it out. Thanks.

IDoc basic type FIDCCH01 with error F5866

Iu2019m trying to create an iDoc with basic type FIDCCH01 and message type FIDCCH type. Iu2019m getting error F5866 u201CWhen calling up the interface to financial accounting, no entry was made in the transfer parameter "Application key" when I process the idoc. I do not see an idoc value by this name. What am I missing in my config?
Thanks,
Stan

Stan,
First, I'd like to mention that you determine where the error message F5866 is used by entering this message in transaction SE91 and pressing the where-used function. This won't show you any of the dynamic message calls, but it does indicate that function modules FI_DOCUMENT_CHANGE and FI_DOCUMENT_CHECK_CHANGE are both possible origins for the message you received. These function modules are part of the FI Interface which I am assuming is called during the processing of your IDoc.
ACCHD-AWREF is one of the values passed to the FI Interface function modules, and message F5866 is returned when that field is blank. This is why I assume that the IDoc in question is missing a value for the AWREF field.
Based on that assumption, I checked the definition for the IDoc type that you mentioned, FIDCCH01, via area menu WEDI. This IDoc type contains a segment E1FIREF with field AWREF. You can use transaction WE02 to display the IDoc causing the error and check to see if the actual data for E1FIREF-AWREF is blank (ultimately leading to the blank ACCHD-AWREF value and error F5866).
Cheers,
Jamie

CLFMAS Basic type (IDOC)

Hi,
BD10 is used to send material master and message type MATMAS can be used for it.
Like that i want to send data related to basic type CLFMAS01 and message type CLFMAS
which transaction should i use.
Rgds,
Ganesh

Hello,
For classification use BD93 transaction but make sure your distribution model is set up.
<removed by moderator>
Edited by: Thomas Zloch on Dec 9, 2010 2:43 PM - please do not ask for ...

Prob wth Extending HRMD_A06 basic type

Hi All,
I have some custom fields in PA0002 table. So i extended HRMD_A06 and in user-exits i am populating custom fields. Out bound side everything is OK. But it is giving 51 error in inbound side. Probelm with read_namtb subroutine. it is chking the custom segment in T777D table...
I am unable to solve the problem. Can anyone hlp me in this regard.

May be this helps you !!

FYI
SymptomThe standard scenario for the distribution of HR master data and organizational data via message type HRMD_A only covers a limited number of infotypes.
Additional standard infotypes should be distributed using a customer enhancement.
Other terms
PFAL, RHALEINI, HRMD_A
Reason and Prerequisites
In the standard scenario, only infotypes are distributed, which are required for a distributed HR in a non HR-system.
Solution
The following activities are required if standard infotype Pnnnn (with nnnn = infotype number) is to be distributed in addition.
Consider the restrictions at the end of this note in particular!
Release 3.1
1. Source code corrections:
According to the attachment (programs not contained in the standard system), repairs are necessary in the Includes LRHA2U06 and UP50RU01.
You only have to change Include UP50RU01 if it is a PA infotype.
If you also want to distribute infotypes starting with 2nnn or 9nnn, an additional repair in Include LRHALF01 is necessary. Remember that in this case the Infotype 2011 is stored differently than the other infotypes and cannot therefore be distributed.
Note that these changes are not contained in the standard system.
2. Customizing:
Transaction WE31 for Z1Pnnnn (in the sending system and the receiving system):
For each additional infotype, create a new segment type Z1Pnnnn (with nnnn = infotype number).
Transaction SM30 for table T777D only for PD infotypes (in the sending system and the receiving system):
For the entry infotype nnnn, enter Z1Pnnnn in field IDOC segment.
Transaction WE30 for ZRMD_A01 (in the sending system and the receiving system):
With Transaction WE30, create extension ZRMD_A01.
Create E1PITYP as a reference segment type, as child segments of this, the extension segment types Z1Pnnnn. As an IDoc type, create ZRMD_A01 for the basic IDoc type HRMD_A01 and extension ZRMD_A01.
Transaction WE82 (in the sending system and the receiving system):
The entry for message type HRMD_A and basic IDoc type HRMD_A01 is copied to a new entry with the extension ZRMD_A01.
Transaction WE20 (in the sending system):
In the sending system, for the partner number of the receiving system in the outbound parameters, enter ZRMD_A01 as idoc type in the line for entry message type HRMD_A.
Transaction WE57 (in the receiving system):
Copy the entry for function module name IDOC_INPUT_HRMD, basic IDoc type HRMD_A01 and message type HRMD_A, and enter ZRMD_A01 in the field extension.
As of Release 4.0B
1. Source code corrections:
Implement the attached advance corrections or:
Apply Hot Package for 4.0B: SAPKH40B02 or
Legal Change Patch for 4.0B: SAPKE40B02
The Include UP50RU01 must only be changed if it is a PA infotype.
Include UP50RU01 is not contained in the Hot Package and must be changed in accordance with the advance correction if the Legal Change Patch is not applied.
After applying the Hot Package (and manually repairing the UP50RU01) or the Legal Change Patch, only the Customizing activities are necessary.
2. Customizing
Transaction WE31 for Z1Pnnnn (in the sending system and the receiving system) :
For each additional infotype, create a new segment type Z1Pnnnn (with nnnn = infotype number). The function "Create by copying" can be used to reduce the work load.
Transaction SM30 for table T777D (in the sending system and the receiving system):
For entry infotype nnnn, enter Z1Pnnnn in field IDOC segment.
Transaction WE30 for ZRMD_A02 (in the sending system and the receiving system):
With Transaction WE30, recreate extension ZRMD_A02.
The linked basic type is HRMD_A02. Insert the new Z1Pnnnn segments as child segments of E1PITYP.
Transaction WE82 (in the sending system and the receiving system):
Copy the entry for message type HRMD_A and basic type HRMD_A02 to a new entry with extension type ZRMD_A02.
Transaction WE20 (in the sending system):
In the sending system enter ZRMD_A02 as an 'Extension' for the partner number of the receiving system in the outbound parameters in the entry message type HRMD_A with basic type HRMD_A02.
Transaction WE57 (in the receiving system):
Copy the entry for the FM name IDOC_INPUT_HRMD, basic type HRMD_A02 and message type HRMD_A, and in field 'Extension' enter ZRMD_A02.
As of Release 4.5A
Here, the Customizing activities described in Release 4.0B are to be carried out.
As of Release 4.5A, HRMD_A03 is used as the basic type and ZRMD_A03 is used as the extension type.
As of Release 4.6A, HRMD_A04 is used as a basic type and ZRMD_A04 is used as an extension type.
As of Release 4.6C, HRMD_A05 is used as a basic type and ZRMD_A05 is used as an extension type.
As of Release 4.70, HRMD_A06 is used as a basic type and ZRMD_A06 is used as an extension type.
Restrictions:
SAP cannot offer any support concerning compatibility with different releases for the additional infotypes of the enhancement in the standard system. For release specific changes to the infotypes of the enhancement a client-specific solution must be found (project solution).
Other known restrictions:
Known restrictions are listed here with possible solution approaches. If you should discover a restriction that is not yet documented, you can inform us of this via the R/3 SAPNet Frontend with a low priority problem message.
01/25/1999: PA infotypes with subtypes are not found in T591A
For infotypes in personnel administration, whose subtypes are stored in a different table than T591A according to table T582A, distribution works in the transfer mode 'Insert' and using the change pointers. Distribution in the transfer mode 'Update' does not work. The approach to solve the problem is a customer-specific extension of the routine HR_INFTY_GET in program RHALEINI by the corresponding infotype/subtype combinations.
02/01/1999: Workflow infotypes
Workflow infotypes, thus in the area 12xx, are not supported since the object type workflow is not supported in the standard ALE scenario. The approach to solve the problem is the use of the manual transport connection (RHMOVE30).
05/17/1999: Infotype 2011
The Infotype 2011 is stored differently than the other infotypes and therefore cannot be distributed.
11/09/2000: Segment for infotypes with a width of more than 1000 characters
The maximum width of a segment is 1000 characters. For this reason it cannot be generated automatically for infotypes with a width of more than 1000 characters.
A possible solution is to create the segment manually and to only insert the key fields and the application fields that are really needed in the segment in order to avoid exceeding the 1000 characters. The values of the fields are transported from infotype into the segment and vice versa in the case of infotypes that are distributed additionally. The reason is that the fields have the same names in segment and infotype.
07/17/2002: In ALE inbound processing, only the data records of the infotypes are posted - similar to the infotypes to be distributed in the standard. No additional functions regarding possibly dependent or derived data in other (database) tables are executed. A solution approach is to distribute the dependent or derived data in a separate (customer) scenario or implement a customer exit (RHALE001) or a BADI (HRALE00INBOUND_IDOC) with the desired functionality.

Extending basic type SDPIID01

Hi,
I have to extend basic type SDPIID01 and add custom segments, After adding those segments I need to update records in those custom fields that would get stored in the databse table using Idoc.Pls suggest the complete steps and the any enhancement or exits that I need to implement to update the values in the database.Also pls suggest the logic that needs to be written inside that enhancement, exit or BADI.
Thanks in advance
Anand

Hi go to we30
Give one zidoc type name and create with radio button extension.
Choose create newlinked basic type , give ur basic type as SDPIID01
Then enter description and say ok.
and save .
Now Clk on the segment under which u want to add ur zsegment wether u want to add on hraedr level or item level.
and click on craete .
Enter a segment name , minimum1 maximum u can gv as per u like 10 , 99 etc.and ok.
It will take u to the segment structure , where u have to add the zfields.
For detail u can go through some documents or helps.
Regards

Restructuring the basic IDoc type DELVRY03

Hi experts,
My rek is to restructure the Basic Idoc type DELVRY03 for outbound delivery.
I am using IDOC_OUTPUT_DELVRY.
Is there any exit or badi for this.
Thanks

we31:
Create your new segment.
Save and remember release (edit-set release)
we30:
Create your new idoc type. Create like extension.
In your linked idoc type fill your standard idoc type.
Press create new sement button for add segments and put your Z segment created in we31 with min and max quantity.
Save and release the idoc type
Regards

IDoc type "DELVRY03" for INBOUND delivery confirmation and Outbound Deliver

Hi ,
We have a requirement where we have to send Inbound delivery confirmation as well as outbound delivery notification to our same customer. (3PL case)
We have a EDI partner who is receiving our messages and transforming them before sending it to customer.
Now my problem is , since I am using same idoc type (DELVRY03) for both cases therefore wondering how my EDI partner will differentiate whether received message is a INBOUND delivery confirmation or OUTBound delivery notification.
regards
Shrey

Thx for your reply ...
Wondering about the impacts , if I create a new message type like ZDESADV and attach it to DELVRY03.
In this i could have two message types DESADV and ZDESADV.
Will it impact anywhere ?
Regards
Shrey

IDOC question on Message type and Basic Type - Partner Profile

Hi all,
I am wonder if I can post any IDoc question in this right forum/module. If not please direct me to the right forum/module. I am a newbie in IDOC setup.
My question is about the setup of Partner Profile creation (WE20).
When creating a new partner, for example with partner type LI, I notice there is outbound parameter and inbound parameter.
Questions:
1 u2013 It makes sense to have only one message type record appear in EITHER one of these two tables. I notice that some partner in my system has message type record exist on both the inbound and outbound parameters table, why system allows? What is the business rational?
2 u2013 May I have a list of standard SAPu2019s Message Type object of its usage description, and its allowable Basic Type (ie. IDOC TYPE). Basically a website to describe their (i.e. Message type and its Basic Type) business usage.
Thanks.
tuff

Tuff,
Below are my thoughts,
There is a partner sing partner type LI. This partner in the WE20, has one record (i.e. with Message Type ORDERS) exist in the Outbound Parameter table. This partner also has 4 records (i.w. with Message Type DESADV, INVOIC, MBGMCR, and ORDRSP) exist in the Inbound Parameter table. So my question is what is the business rational behind this kind of setup. Because I am confuse when come to create a partner profile, whether I need to create a message type in Inbound Parameter table or Outbound Parameter table, or I need both.
OK, so looking at the above example, you have an orders message type(This is for creating an order) in the outbound, this means that you are sending out an IDOC(purchase order for ex) to this partner, so that this partner can create an SO in his system and fulfill your order.
Now you also, mention that you have other four Message types for the same partner on the inbound, now let us look at the above scenario, you have asked your partner to fulfill the order, i guess you would like to get a confirmation from him/her if the order was created or not in his/her system and how and when is he/she going to fulfill your order requirement. This he/she does by sending an response to your order - ORDRSP.
And when the partner is ready to ship your order to you, he/she sends out a Advance Shipping Notice - ASN via the IDOC of message type DESADV.
Finally and most importantly , he/she will send you the invoice - INVOIC for the order.
In general, you interact with your partner via Business Docs - Order, Delivery, ASN, Invoice etc, so whatever document come from your partner - ORDRSP, INVOIC etc will be on the inbound profile of the partner. Whatever docs that you send ORDERS, ORDCHG etc etc will be on the outbound profile of the partner.
2 - Bascially I would like a reference in any website that allow me to choose which message type is best use for my partner profile, so that I don't have to reinvent.
Well, there is no choice of choosing/best message type for a given requirement - So for sending an Invoice the message type is INVOIC, ORDERS - For order creation, ORDCHG for order change etc. However the IDOC type, is some thing that you can choose, for Ex: ORDERS01 - ORDERS05, these are the IDOC types that are available, so if you are interacting with a partner who are running an old version of SAP and their system has only upto ORDERS02 in their version of SAP then you would use ORDERS02.
Regards,
Chen

IDOC and Basic Type

Hi Experts,
I have a basic type that I will use in my IDOC with no process codes(attached FM) that will create a document (e.g. orders, deliveries)... and I have found out a BAPI that I can use in creating the document.. the question is.. do I still need to CALL FUNCTION 'IDOC_WRITE_AND_START_INBOUND' after calling the BAPI to create the document?
Thanks!
Nosaj

Hi,
Thanks. To clarify.. first I will receive an IDOC coming from XI this IDOC containes the planned orderse that I will create in SAP.
Question: Can one IDOC contains a lot of planned orders to be created? Meaning that I have created a copy of segment E1PLAFL because this segment can only acquire a maximum of 1 data record... so i copy it and customize it to acquire more than 1 data records.....?
Then the Basic Type: LOIPLO01 does not have a functionaly of creating planned orders.. so I will use a BAPI in creating the planned orders....
Question: Since I will be using a BAPI to create the IDOC.. do I still need to call the function module ive said (WRITEIDOC)?

Basic type DELVRY03 and FM IDOC_INPUT_DELVRY

Similar Messages

Maybe you are looking for