ORI vs CHA qualifier in DELVRY or SHPMNT IDoc's

Hi,
I was checking to find a way to make ORI qualifier iinto CHA qualifier in segment E1EDL18 in delvry or E1EDT18 in shpmnt. Is there any configuration to obtain the CHA qualifier when we re-issue an output after performing changes. I find the qual to be ORI even though I make changes in the delivery document and repeat the output.
thanks,
Kumar.

Hi Jaya,
BAPI_TRANSACTION_COMMIT and BAPI_TRANSACTION_ROLLBACK can be used to finish the database update (or rollback) process.
BAPI_TRANSACTION_COMMIT will trigger all pending update processes, all PERFORM ON COMMIT, just all database changes in current LUW.
Generally, BAPI_TRANSACTION_COMMIT or COMMIT WORK should be the last action in the logical unit of work. If you do it multiple times, you can't rollback anything in case of error occurred after COMMIT.
NEVER use BAPI_TRANSACTION_COMMIT in a function module because you don't know what has been done before the call and what will come later.
Regards,
Clemens

Similar Messages

Inbound processing of segment E1EDT13 - QUALF 499 in SHPMNT idoc

Dear all,
we are currently facing the problem, that we want to send customized deadline dates in a SHPMNT idoc into our system.
I set up the customizing accordingly, maintained the data in a outbound delivery and created an idoc out of it. I saw, that the segment E1EDT13 is filled using QUALF 499.
I took this idoc modified a few fields and sent it back as an inbound delivery.
This works, but E1EDT13 with qualifier 499 doesn't appear in the created inbound delivery.
I checked the coding of the inbound function modules concerning qualifier 499 and detected, that this qualifier is never considered in the coding.
Does SAP support the inbound posting of qualifier 499? If yes, how? Which function module will be used?
If no, does anyone have an idea/experience concerning inbound SHPMNT using qualifier 499 in segment E1EDT13?
Kind regards
Harry
PS: We are using a ECC 6.0 release.
PPS: I posted the wrong idoc type in a previous message.

Posted the wrong idoc type. Sorry
Moderator Message: I will lock this thread, just in case someone feels tempted to answer it :-). Next time please use the EDIT option to edit your post.
Edited by: kishan P on Nov 4, 2010 5:53 PM

Shipment is not updating using SHPMNT IDoc

Hello All,
I am updating a Shipment with only one delivery using IDoc SHPMNT05, however this Shipment has two deliveries earlier, As a result IDoc failed with as error message : This action no longer possible: Transport XXXXXXXXX has already been scheduled. This error is because this shipment status is set to planned.
But I want to update the shipment with only one delivery even though it is scheduled. ideally when this IDoc is posted one delivery should be unassigned from the shipment. how can I achieve that, please help me.
Thanks & Regards
RK
Edited by: RK on Jul 1, 2010 11:50 AM

Hi Maris Sauka,
If Shipment is already scheduled, standard SAP does not allow to add , move or delete the deliveries from it, it gives error like "This action no longer possible: Transport XXXXXXXXX has already been scheduled" , This error comes from Function module SD_SHIPMENT_FCODE_CONTROL,To overcome this there is an implicit enhancement required in form statement shipment_fcode_allowed in include program LV56EF01. within this I clear the shipment planning status i_xvttk-stdis.
Note: Please make sure that this enhancement does not impact any other developments, so make use of export and import statements.
Thanks
RK

Error while processing SHPMNT in using big pack size 20 but not if 1

Hi Experts,
I am trying to to process status 64 SHPMNT IDocs via background job using program RBDAPP01.
When I try to use Pack Size 20 (minimum preferred/suggested by SAP for better performance), I am encountering the status 54 error message "Processing terminated because not required or possible" when the SHPMNT IDocs are pointing to the same Shipment document.
According to the error message:
Processing of this IDoc is terminated because it is unnecessary or impossible. Reasons for termination may include:
1. The IDoc appears twice in the IDoc packet you just processed
2. The data included in the IDoc you entered does not provide unique identification of the application document concerned. For example, you enter the primary identification using field EXTI1. There could be two application documents with the same 'external identification 1'. In this case, there would be no way to tell which document should be changed.
So, I got the idea of trying Pack Size 1 and it worked!
So in conclusion, SAP (by default) does not allow processing of multiple SHPMNT IDocs referring to the same Shipment document in one packet.
Is it possible to disable/turn off this check so that SHPMNT IDocs will be processed using Pack Size 20 even if they are referring to the same Shipment?
Thanks and Regards,
Ruix

Hi Ruix,
We are running to exactly similar problem, Can you please share how you have resolved this issue?
Many thanks in advance!!!!
Regards,
Kumar

Read IDOC segment with qualifier

Hi,
I need to read data into a workArea from a IDOC segment which has Qualifiers for it.
The IDOC or BASIC type is   DELVRY03.
Segment                                E1EDT13.
Qualifier                                 006
Thx in advance
Mac

DATA:
lx_e1edt13      TYPE e1edt13.
FIELD-SYMBOLS:
<fs_idoc_data> LIKE LINE OF idoc_data.
LOOP AT idoc_data ASSIGNING <fs_idoc_data> WHERE segnam = 'E1EDT13'.
lx_e1edt13 = <ls_idoc_data>-sdata.
IF lx_e1edt13-qualf = '006'.
your code
or get the data into internal table as per your requiremnt
ENDIF.
ENDLOOP.

IDOC - segment Qualifier

Dear all,
Do you know the transaction or an document which give the link between the Qualifier segment of an segment IDOC and the SAP field ?
for example : IDOC ORDERS05
segment E1EDK03
qualifier 002 : wished delivery date in VA01
segment E1EDK02
qualifier 050 : Delivery Order in segment description but correspond to PO number in VA01
I search to fill in the field PO Date but I don't find the qualifer segment.
Could you please help me ?
thanks
Véronique

Hi friends,
i thing your problem will solve.
E1EDK01 : IDoc: Document header general data
Segment definition E2EDK01005 Released since Release 45B , Segment length: 0357
ACTION : Action code for the whole EDI message
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
KZABS : Flag: order acknowledgment required
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 002, Offset : 0066. external length : 000001
CURCY : Currency
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 003, Offset : 0067. external length : 000003
HWAER : EDI local currency
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 004, Offset : 0070. external length : 000003
WKURS : Exchange rate
internal data type : CHAR
Internal length : 000012 characters
Position in segment : 005, Offset : 0073. external length : 000012
ZTERM : Terms of payment key
internal data type : CHAR
Internal length : 000017 characters
Position in segment : 006, Offset : 0085. external length : 000017
KUNDEUINR : VAT Registration Number
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 007, Offset : 0102. external length : 000020
EIGENUINR : VAT Registration Number
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 008, Offset : 0122. external length : 000020
BSART : Document type
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 009, Offset : 0142. external length : 000004
BELNR : IDOC document number
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 010, Offset : 0146. external length : 000035
NTGEW : Net weight
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 011, Offset : 0181. external length : 000018
BRGEW : Net weight
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 012, Offset : 0199. external length : 000018
GEWEI : Weight unit
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 013, Offset : 0217. external length : 000003
FKART_RL : Invoice list type
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 014, Offset : 0220. external length : 000004
ABLAD : Unloading Point
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 015, Offset : 0224. external length : 000025
BSTZD : Purchase order number supplement
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 016, Offset : 0249. external length : 000004
VSART : Shipping Conditions
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 017, Offset : 0253. external length : 000002
VSART_BEZ : Description of the Shipping Type
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 018, Offset : 0255. external length : 000020
RECIPNT_NO : Number of recipient (for control via the ALE model)
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 019, Offset : 0275. external length : 000010
KZAZU : Order Combination Indicator
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 020, Offset : 0285. external length : 000001
AUTLF : Complete delivery defined for each sales order?
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 021, Offset : 0286. external length : 000001
AUGRU : Order reason (reason for the business transaction)
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 022, Offset : 0287. external length : 000003
AUGRU_BEZ : Description
internal data type : CHAR
Internal length : 000040 characters
Position in segment : 023, Offset : 0290. external length : 000040
ABRVW : Usage Indicator
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 024, Offset : 0330. external length : 000003
ABRVW_BEZ : Description
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 025, Offset : 0333. external length : 000020
FKTYP : Billing category
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 026, Offset : 0353. external length : 000001
LIFSK : Delivery block (document header)
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 027, Offset : 0354. external length : 000002
LIFSK_BEZ : Description
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 028, Offset : 0356. external length : 000020
EMPST : Receiving point
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 029, Offset : 0376. external length : 000025
ABTNR : Department number
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 030, Offset : 0401. external length : 000004
DELCO : Agreed delivery time
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 031, Offset : 0405. external length : 000003
WKURS_M : Indirectly quoted exchange rate in an IDoc segment
internal data type : CHAR
Internal length : 000012 characters
Position in segment : 032, Offset : 0408. external length : 000012
E1EDK14 : IDoc: Document Header Organizational Data
Segment definition E2EDK14 Released since Release 30A , Segment length: 0038
QUALF : IDOC qualifer organization
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
ORGID : IDOC organization
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 002, Offset : 0066. external length : 000035
E1EDK03 : IDoc: Document header date segment
Segment definition E2EDK03 Released since Release 30A , Segment length: 0017
IDDAT : Qualifier for IDOC date segment
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
DATUM : IDOC: Date
internal data type : CHAR
Internal length : 000008 characters
Position in segment : 002, Offset : 0066. external length : 000008
UZEIT : IDOC: Time
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 003, Offset : 0074. external length : 000006
E1EDK04 : IDoc: Document header taxes
Segment definition E2EDK04001 Released since Release 40B , Segment length: 0107
MWSKZ : VAT indicator
internal data type : CHAR
Internal length : 000007 characters
Position in segment : 001, Offset : 0063. external length : 000007
MSATZ : VAT rate
internal data type : CHAR
Internal length : 000017 characters
Position in segment : 002, Offset : 0070. external length : 000017
MWSBT : Value added tax amount
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 003, Offset : 0087. external length : 000018
TXJCD : Tax Jurisdiction
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 004, Offset : 0105. external length : 000015
KTEXT : Text Field
internal data type : CHAR
Internal length : 000050 characters
Position in segment : 005, Offset : 0120. external length : 000050
E1EDK05 : IDoc: Document header conditions
Segment definition E2EDK05001 Released since Release 40A , Segment length: 0185
ALCKZ : Surcharge or discount indicator
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
KSCHL : Condition type (coded)
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 002, Offset : 0066. external length : 000004
KOTXT : Condition text
internal data type : CHAR
Internal length : 000080 characters
Position in segment : 003, Offset : 0070. external length : 000080
BETRG : Fixed surcharge/discount on total gross
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 004, Offset : 0150. external length : 000018
KPERC : Condition percentage rate
internal data type : CHAR
Internal length : 000008 characters
Position in segment : 005, Offset : 0168. external length : 000008
KRATE : Condition record per unit
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 006, Offset : 0176. external length : 000015
UPRBS : Price unit
internal data type : CHAR
Internal length : 000009 characters
Position in segment : 007, Offset : 0191. external length : 000009
MEAUN : Unit of measurement
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 008, Offset : 0200. external length : 000003
KOBTR : IDoc condition end amount
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 009, Offset : 0203. external length : 000018
MWSKZ : VAT indicator
internal data type : CHAR
Internal length : 000007 characters
Position in segment : 010, Offset : 0221. external length : 000007
MSATZ : VAT rate
internal data type : CHAR
Internal length : 000017 characters
Position in segment : 011, Offset : 0228. external length : 000017
KOEIN : Currency
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 012, Offset : 0245. external length : 000003
E1EDKA1 : IDoc: Document Header Partner Information
Segment definition E2EDKA1003 Released since Release 45A , Segment length: 0995
PARVW : Partner function (e.g. sold-to party, ship-to party, ...)
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
PARTN : Partner number
internal data type : CHAR
Internal length : 000017 characters
Position in segment : 002, Offset : 0066. external length : 000017
LIFNR : Vendor number at customer location
internal data type : CHAR
Internal length : 000017 characters
Position in segment : 003, Offset : 0083. external length : 000017
NAME1 : Name 1
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 004, Offset : 0100. external length : 000035
NAME2 : Name 2
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 005, Offset : 0135. external length : 000035
NAME3 : Name 3
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 006, Offset : 0170. external length : 000035
NAME4 : Name 4
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 007, Offset : 0205. external length : 000035
STRAS : Street and house number 1
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 008, Offset : 0240. external length : 000035
STRS2 : Street and house number 2
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 009, Offset : 0275. external length : 000035
PFACH : PO Box
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 010, Offset : 0310. external length : 000035
ORT01 : City
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 011, Offset : 0345. external length : 000035
COUNC : County code
internal data type : CHAR
Internal length : 000009 characters
Position in segment : 012, Offset : 0380. external length : 000009
PSTLZ : Postal code
internal data type : CHAR
Internal length : 000009 characters
Position in segment : 013, Offset : 0389. external length : 000009
PSTL2 : P.O. Box postal code
internal data type : CHAR
Internal length : 000009 characters
Position in segment : 014, Offset : 0398. external length : 000009
LAND1 : Country Key
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 015, Offset : 0407. external length : 000003
ABLAD : Unloading Point
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 016, Offset : 0410. external length : 000035
PERNR : Contact person's personnel number
internal data type : CHAR
Internal length : 000030 characters
Position in segment : 017, Offset : 0445. external length : 000030
PARNR : Contact person's number (not personnel number)
internal data type : CHAR
Internal length : 000030 characters
Position in segment : 018, Offset : 0475. external length : 000030
TELF1 : 1st telephone number of contact person
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 019, Offset : 0505. external length : 000025
TELF2 : 2nd telephone number of contact person
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 020, Offset : 0530. external length : 000025
TELBX : Telebox number
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 021, Offset : 0555. external length : 000025
TELFX : Fax number
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 022, Offset : 0580. external length : 000025
TELTX : Teletex number
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 023, Offset : 0605. external length : 000025
TELX1 : Telex number
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 024, Offset : 0630. external length : 000025
SPRAS : Language key
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 025, Offset : 0655. external length : 000001
ANRED : Form of Address
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 026, Offset : 0656. external length : 000015
ORT02 : District
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 027, Offset : 0671. external length : 000035
HAUSN : House number
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 028, Offset : 0706. external length : 000006
STOCK : Floor
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 029, Offset : 0712. external length : 000006
REGIO : Region
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 030, Offset : 0718. external length : 000003
PARGE : Partner's gender
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 031, Offset : 0721. external length : 000001
ISOAL : Country ISO code
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 032, Offset : 0722. external length : 000002
ISONU : Country ISO code
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 033, Offset : 0724. external length : 000002
FCODE : Company key (France)
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 034, Offset : 0726. external length : 000020
IHREZ : Your reference (Partner)
internal data type : CHAR
Internal length : 000030 characters
Position in segment : 035, Offset : 0746. external length : 000030
BNAME : IDoc user name
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 036, Offset : 0776. external length : 000035
PAORG : IDOC organization code
internal data type : CHAR
Internal length : 000030 characters
Position in segment : 037, Offset : 0811. external length : 000030
ORGTX : IDoc organization code text
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 038, Offset : 0841. external length : 000035
PAGRU : IDoc group code
internal data type : CHAR
Internal length : 000030 characters
Position in segment : 039, Offset : 0876. external length : 000030
KNREF : Customer description of partner (plant, storage location)
internal data type : CHAR
Internal length : 000030 characters
Position in segment : 040, Offset : 0906. external length : 000030
ILNNR : Character field, length 70
internal data type : CHAR
Internal length : 000070 characters
Position in segment : 041, Offset : 0936. external length : 000070
PFORT : PO Box city
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 042, Offset : 1006. external length : 000035
SPRAS_ISO : Language according to ISO 639
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 043, Offset : 1041. external length : 000002
TITLE : Title
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 044, Offset : 1043. external length : 000015
E1EDKA3 : IDoc: Document Header Partner Information Additional Data
Segment definition E2EDKA3 Released since Release 30D , Segment length: 0073
QUALP : IDOC Partner identification (e.g.Dun&Bradstreet number)
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
STDPN : Character field, length 70
internal data type : CHAR
Internal length : 000070 characters
Position in segment : 002, Offset : 0066. external length : 000070
E1EDK02 : IDoc: Document header reference data
Segment definition E2EDK02 Released since Release 30A , Segment length: 0058
QUALF : IDOC qualifier reference document
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
BELNR : IDOC document number
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 002, Offset : 0066. external length : 000035
POSNR : Item number
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 003, Offset : 0101. external length : 000006
DATUM : IDOC: Date
internal data type : CHAR
Internal length : 000008 characters
Position in segment : 004, Offset : 0107. external length : 000008
UZEIT : IDOC: Time
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 005, Offset : 0115. external length : 000006
E1EDK17 : IDoc: Document Header Terms of Delivery
Segment definition E2EDK17 Released since Release 30A , Segment length: 0076
QUALF : IDOC qualifier: Terms of delivery
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
LKOND : IDOC delivery condition code
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 002, Offset : 0066. external length : 000003
LKTEXT : IDOC delivery condition text
internal data type : CHAR
Internal length : 000070 characters
Position in segment : 003, Offset : 0069. external length : 000070
E1EDK18 : IDoc: Document Header Terms of Payment
Segment definition E2EDK18 Released since Release 30A , Segment length: 0089
QUALF : IDOC qualifier: Terms of payment
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
TAGE : IDOC Number of days
internal data type : CHAR
Internal length : 000008 characters
Position in segment : 002, Offset : 0066. external length : 000008
PRZNT : IDOC percentage for terms of payment
internal data type : CHAR
Internal length : 000008 characters
Position in segment : 003, Offset : 0074. external length : 000008
ZTERM_TXT : Text line
internal data type : CHAR
Internal length : 000070 characters
Position in segment : 004, Offset : 0082. external length : 000070
E1EDK35 : IDoc: Document Header Additional Data
Segment definition E2EDK35000 Released since Release 45A , Segment length: 0078
QUALZ : Qualifier for IDoc additional data
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
CUSADD : Data Element Type CHAR Length 35
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 002, Offset : 0066. external length : 000035
CUSADD_BEZ : Character field of length 40
internal data type : CHAR
Internal length : 000040 characters
Position in segment : 003, Offset : 0101. external length : 000040
E1EDK36 : IDOC: Doc.header payment cards
Segment definition E2EDK36000 Released since Release 45A , Segment length: 0114
CCINS : Payment cards: Card type
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 001, Offset : 0063. external length : 000004
CCINS_BEZEI : Description
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 002, Offset : 0067. external length : 000020
CCNUM : Payment cards: Card number
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 003, Offset : 0087. external length : 000025
EXDATBI : IDOC: Date
internal data type : CHAR
Internal length : 000008 characters
Position in segment : 004, Offset : 0112. external length : 000008
CCNAME : Payment cards: Name of cardholder
internal data type : CHAR
Internal length : 000040 characters
Position in segment : 005, Offset : 0120. external length : 000040
FAKWR : Maximum amount
internal data type : CURR
Internal length : 000015 characters
000002 decimal places, without sign
Position in segment : 006, Offset : 0160. external length : 000017
E1EDKT1 : IDoc: Document Header Text Identification
Segment definition E2EDKT1002 Released since Release 45A , Segment length: 0089
TDID : Text ID
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 001, Offset : 0063. external length : 000004
TSSPRAS : Language Key
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 002, Offset : 0067. external length : 000003
TSSPRAS_ISO : Language according to ISO 639
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 003, Offset : 0070. external length : 000002
TDOBJECT : Texts: Application Object
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 004, Offset : 0072. external length : 000010
TDOBNAME : Name
internal data type : CHAR
Internal length : 000070 characters
Position in segment : 005, Offset : 0082. external length : 000070
E1EDKT2 : IDoc: Document Header Texts
Segment definition E2EDKT2001 Released since Release 40A , Segment length: 0072
TDLINE : Text line
internal data type : CHAR
Internal length : 000070 characters
Position in segment : 001, Offset : 0063. external length : 000070
TDFORMAT : Tag column
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 002, Offset : 0133. external length : 000002
E1EDP01 : IDoc: Document Item General Data
Segment definition E2EDP01007 Released since Release 640 , Segment length: 0542
POSEX : Item number
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 001, Offset : 0063. external length : 000006
ACTION : Action code for the item
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 002, Offset : 0069. external length : 000003
PSTYP : Item Category
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 003, Offset : 0072. external length : 000001
KZABS : Flag: order acknowledgment required
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 004, Offset : 0073. external length : 000001
MENGE : Quantity
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 005, Offset : 0074. external length : 000015
MENEE : Unit of measure
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 006, Offset : 0089. external length : 000003
BMNG2 : Quantity in price unit
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 007, Offset : 0092. external length : 000015
PMENE : Price Unit of Measure
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 008, Offset : 0107. external length : 000003
ABFTZ : Agreed cumulative quantity
internal data type : CHAR
Internal length : 000007 characters
Position in segment : 009, Offset : 0110. external length : 000007
VPREI : Price (net)
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 010, Offset : 0117. external length : 000015
PEINH : Price unit
internal data type : CHAR
Internal length : 000009 characters
Position in segment : 011, Offset : 0132. external length : 000009
NETWR : Item value (net)
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 012, Offset : 0141. external length : 000018
ANETW : Absolute net value of item
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 013, Offset : 0159. external length : 000018
SKFBP : Amount qualifying for cash discount
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 014, Offset : 0177. external length : 000018
NTGEW : Net weight
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 015, Offset : 0195. external length : 000018
GEWEI : Weight unit
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 016, Offset : 0213. external length : 000003
EINKZ : Flag: More than one schedule line for the item
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 017, Offset : 0216. external length : 000001
CURCY : Currency
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 018, Offset : 0217. external length : 000003
PREIS : Gross price
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 019, Offset : 0220. external length : 000018
MATKL : IDOC material class
internal data type : CHAR
Internal length : 000009 characters
Position in segment : 020, Offset : 0238. external length : 000009
UEPOS : Higher-Level Item in BOM Structures
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 021, Offset : 0247. external length : 000006
GRKOR : Delivery group (items delivered together)
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 022, Offset : 0253. external length : 000003
EVERS : Shipping instructions
internal data type : CHAR
Internal length : 000007 characters
Position in segment : 023, Offset : 0256. external length : 000007
BPUMN : Denominator for Conv. of Order Price Unit into Order Unit
internal data type : DEC
Internal length : 000005 characters
No decimal places, without sign
Position in segment : 024, Offset : 0263. external length : 000006
BPUMZ : Numerator for Conversion of Order Price Unit into Order Unit
internal data type : DEC
Internal length : 000005 characters
No decimal places, without sign
Position in segment : 025, Offset : 0269. external length : 000006
ABGRU : Reason for rejection of quotations and sales orders
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 026, Offset : 0275. external length : 000002
ABGRT : Description
internal data type : CHAR
Internal length : 000040 characters
Position in segment : 027, Offset : 0277. external length : 000040
ANTLF : Maximum number of partial deliveries allowed per item
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 028, Offset : 0317. external length : 000001
FIXMG : Delivery date and quantity fixed
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 029, Offset : 0318. external length : 000001
KZAZU : Order Combination Indicator
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 030, Offset : 0319. external length : 000001
BRGEW : Total weight
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 031, Offset : 0320. external length : 000018

SHPMNT question

Hi Expert,
I need help. I would like to send SHPMNT idoc when i click the shipment start to respective pipe. We are having this senario, 1 decentralized system with 2 ERP. But at the output type is throwing this error.
Too many recipients found for message type SHPMNT in the ALE model
Message no. B1130
Diagnosis
In the ALE distribution customer model several recipient systems for IDOCs with message type SHPMNT and filter object type 'LIFNR' with value 'WMIIVENDOR' have been modeled from this system, but only one recipient system is allowed.
Procedure
Please change the ALE distribution customer model so that it allows only one recipient system for the message from this system.
Any expert encounter this error before? If yes, could you advise on the solution?
thanks
Hooi Fung

The message already tells you exactly what to do. You have to maintain a filter for the message type in BD64 transaction. The document is supposed to be sent to one recipient. If SAP doesn't find that recipient, it throws an error message. Naturally, you also have to maintain partner profiles in WE20.

Parrllel IDOC gets generated.

Hi Experts,
In one of my requirement we need to create IDOC in XML format and place it in the unix file path.It was working fine but we have noticed that rarely for few deliveries a parallel IDOC gets triggered with along with the original IDOC. It carries the qualifier ORI or CHA in the field segment E1EDL18 (Segment 000005). We don't want this to be created. Please pass on suggestion to avoid the generation a parallel idoc along with the originals.
Regards,
Emaya

Hi,
Can you please share your experiences of using HPR transactions, any problems or any special things that need to be kept in mind while executing these transactions.
Thanks.

EDI Transaction set for Serial numbers

We are currently using 810/850/856 for communicating with our customers. We now need to send the serial numbers also to the customers. What EDI transaction set do we need to use? Any helpful links?
Thx.

Hope you are aware EDI 850 is for PO. How that is relevant for Sales Order(Outbound)
Well, EDI 856 is for Advance Shipping Notification. Where
Std Logical Message Type
Std IDoc Types
SHPMNT or SHPADV
SHPMNT01
SHPMNT02
SHPMNT03
DESADV
DELVRY01
DELVRY02
As I already mention in my previous post that you need to check the respective IDoc do you have segment E1EDL11 is the IDoc for Serial Number field SERNR.
If the said segment is not there, then extend the IDoc for the desired segment.
Else, check whether serial number is getting populated in respective qualifier or not in outbound IDoc message.
If serial no. value is not getting populated, then investigate why that is not happening? Whether you need a little enhancement to enable that? Or probably you don't have serialized material for the said business process.
Thanks,
JP

Output type not created for outbound delivery while using SHMNT05 idoc type

Hi Experts,
Please help me to solve the below issue.
Problem:- I want to to generate an IDOC(using type SHPMNT06) once the PGI is done for an outbound delivery.
Already it is working fine when used DESADV.DESADV01 or DESADV.DELVRY07. But now the output type is not getting created when used SHMNT.SHPMNT06. I have created a separate output type ZPJ7 just as a mirror copy of the earlier output type(ZPJ6) used for DESADV.DELVRY07.
Question:- Is it possible to use idoc SHPMNT06 instead for DESADV01 or DELVRY07? If yes then what are steps to be followed?
The reason why SHPMNT06 idoc is planned:- We have a scenario to send outbound delivery to 3rd party system via XI. If the outbound delivery is for National(Not for Export) and PGI is completed then send the idoc straight forward to XI otherwise DO NOT generate the idoc, but just create the delivery. Collect all the deliveries in a transport and send it in a shipment. The shipment details can be sent using SHPMNT idoc. Now from XI perspective, if we can utlitze the same SHPMNT idoc for the National delivery(1st case) then perhaps this will require less effort. Hence shipment idoc is required to be generated when the delivery is created and PGI is done.
Also it would be great if you can advice some better way to solve above mentioned scenario.
Many Thanks,
Sanjay

There could be several reasons. Go to the document and in the extras-output check output determination analysis in the processing log.
If the output has been created successfully then you need to see your printer determination. Ask basis to check it up. If the problem is that even the print preview is not coming. Check your communication in the output analysis and ensure LOCL is selected. Any other printer will need to be configured.
If thats done already then check whether you have maintianed the condition record.
If that too is done then check whether your output type has been assigned to the output procedure and that the output type is listed in the procedure.
regds
Jude

How SAP integrate with XML interface & Easyship applications for labelling

Dear All,
My client has a requirement to use DHL for its shipments and shipment labelling is required.
However, as per DHL's response that DHL Express label is a complex presentation that does not lend itself the standard labeling options under SAP, but both options of the XML interface and the Easyship applications do provide this label built by the application and delivered to SAP print stream.
Please help to advise if there is any possible solutions for this implementation without using middleware?
Appreciate it.
Thank you.

i AM NOT SURE IF i AM GETTING THIS RIGHT BUT, YOU WILL HAVE TO USE A BUSINESS COMMUNICATOR (EAI) BETWEEN dhl AND saP.In our current client we have developed an application where on PGI of the delivery will trigger a dlvry03 IDOc which passes through the logic of EAI and is then passed onto the carrier labelling system/interface.Once again once we receive back the info from the carrier an inbound IDOc is created to update the delivery with the tracking number and a Fedex label prints directly on the required printer.
Same way you can use shpmnt IDOC and have you tried XSI interface, it was particularly developed to deal with carrier interface.Please let me know I can provid emore info regarding XSI.

Hey I need your help

I am going to create an IDOC when shippijg document reversal is generated due to VL09.
Can anybody help me ...what will bw the segments....wot will be the fields in each of them....i.e the complet idoc type......

process Code SD11
Message type SHPMNT
IDOC Typ SHPMNT05
Regards

Output types for Shipments

Hello All,
I have a unique situation and need your inputs to identify possibilities in resolving it.
Here is the situation:
The transportation planning (TPE system) at our client is done by a 3rd party software. Now, we receive a Sales Order from a customer; create a delivery. TPE system creates the shipments and we PGI it and the sales order follows through the next steps. The shipments created from TPE go to Carriers and they carry the product from our warehouse to pool points from where customers pick it up. We have to pay the carriers from moving our goods from our warehouse to pool points. Thus whenever a shipment is created, we check-in...do the next steps in WM and finally when the shipment is ready, it triggers a payment IDOC to be sent to finance (an external system) so that it can be matched with Carrier invoices and then paid.
Our unique problem: There is a carrier (lets call it NCP) who is moving our goods from warehouse to pool point. We got a sales order from customer. This customer doesn't pick up goods from the pool point. He wants it to be delivered to his distribution center and to do this he is using the same transportation carrier (NCP). Thus when we received the sales order from customer, TPE system created a master shipment (5000001M) for NCP to pick up from our warehouse and deliver to pool point. You might be aware that TPE optimizes the route and thus combines multiple deliveries into one master shipment. From here NCP should pick up a part of the master shipment and deliver it to client. Thus SAP automatically created a sub-shipment (5000002S). This sub-shipment is a part of the master shipment and thus will not be separetely processed in WMS. The master shipment is checked-in, loaded and shipment ready - thus creating a payment IDOC to the external payee system. As the Sub-system is a part of master shipment, it is not touched and thus no payment IDOC is created.
Now the carrier sents two invoices - one for master to pick up goods from our warehouse and deliver it to pool point and the second one - to deliver a part of this shipment to customer's DC. Our payment system is unable to match it up with any IDOC's as we didn't send them out from SAP.
So this is where I'm struck. How should I configure the output for a sub-shipment so that it'll be triggered as soon as the delivery is PGI'ed? Could anyone give some inputs here?
Please let me know if more clarification is needed. Thanks in advance for looking into this.

Chandrasekhar,
Thanks for your inputs, here are the clarifications you've asked for:
1) Sub- shipment is not a SAP object right? Or is it?
- Yes Sub-Shipment is an SAP object. All the shipments are created in TPE (Transportation Management System) by combining deliveries and sent to SAP (SHPMNT Idoc). SHPMNT creates the shipments for each deliveries within SAP. Master Shipments are picked up in WM and processed as per the requirements in the shipment (i.e. packaging etc)
2) You do PGI from shipment and not from delivery right?
- PGI is done on delivery after shipment start/end is completed in WM.
3) What do you mean when you say " .... when the sub-shipment is created but that might cause issues as Carriers can bill us even before the shipment is delivered to client". Carrier won't bill you when sub-shipment is created, right, so you are ahead of the carrier any ways.
- I meant if I create an output type and trigger it as soon as the sub-shipment is created in SAP (from the incoming SHPMNT Idoc), the payment idoc will hit our carrier payment system and is ready to go. Lets assume the carrier sends in an invoice (210), carrier payment system will honor it (it has no visibility on SAP - its an external system). Thus we cannot trigger the payment idoc (858) until the PGI is done on the delivery (to which the sub-shipment is attached).
The situation is:
Master Shipment (500001M) = Delivery 1 + Delivery 2 + Delivery 3 (This should go to customer from pool point - thus sub-shipment 500002S for the same carrier) + Delivery 4 + Delivery 5. This shipment is to delivery from Warehouse to Pool Point.
500001M is handled by WM. They pick/pack and ship. Once the shipment is started, automatically all deliveries are PGI'ed (automatic process). In this process 500002S isn't touched by WM coz they don't have to. So this just stays like that. Because unpacking and re-packing into sub-shipment is the responsibilty of NCP. We just pay for the costs to deliver it to customer's DC.
Now I have to issue output at the shipment level -> because carriers get the shipments (204) and generate invoices (210). Thus I need to generate an output (858) at the sub-shipment level whenever the delivery (to which it is tied to) is PGI'ed (by the automatic process from WM when the master shipment is complete). How can I configure this? The suggestion you gave is to handle the output at delivery level but I cannot do that because the payment instruction is to pay only for the sub-shipment i.e. from pool point to customer's warehouse. But delivery is tied to both master shipment and sub-shipment because this particular product has to go from wareshouse to customer.
You said, we can issue an output at sub-shipment level. Do you know how can I issue the output when the delivery is PGI'ed? Both are independent objects within SAP and also note that none of the tasks within this sub-shipment will be touched by WM. Thus I cannot directly create a condition based on an activity profile.
I hope I'm making some sense.

Packing from Decentralized WMS

We are working on decentralized WMS integration with non-SAP system. We have a problem now - SAP doesn't allow to create handling units for shipment received with SHPMNT IDoc from an external warehouse.
What is a process planed within decentralized WMS, how packages can be created, if we want to put in a single handling unit items from different deliveries?
We planned to use shipment document for that, but now because of error saying "The handling units for the item that is to be packed are maintained in another (decentralized) system. It is not possible to pack in this system." it's not clear anymore
Thanks
Maris

Thanks for answering, but can you please be more specific?
We are planning to follow that procedure:
1) SAP sends outbound deliveries to WMS
2) WMS sends back confirm decentral for goods issue
3) WMS sends shipments with packing data, where in handling units several deliveries are packed together
We cannot use packing for deliveries with confirm decentral idoc, because WMS packs in single handling units items from different deliveries. They pack the goods the most efficient way and if several deliveries has to be delivered to customer, then WMS packs them all together.
What is the procedure that you have?

Mapping EDIFACT to IDoc: IFTMIN to DELVRY / SHPMNT

Hi,
because we haven't done this before we want to ask if there is someone whos has done this before us.
So our business case is that we have to map IFTMIN to any appropriate SAP-Format.
We found that SHPMNT might be the best solution but as we checked the structure we saw that this IDoc contains so much overhead information that we thought we might map it to DELVRY - whereas this is included in SPHMNT.
So has someone of you done this before and can give us a hand on how to map this? maybe there is a mapping template to offer?
I know this sounds silly - but maybe someone might help.
We are also open to any other suggestions on how to map IFTMIN - perhaps to a BAPI?!
br

Hi Fritz,
This blog gives you the realtion between most EDIFACt messages and sap idocs:
/people/community.user/blog/2009/10/12/mapping-idocs-to-x12-transactions-and-edifact-messages
It says SHPMNT04 is the IDOC for Inbound Interfaces and DESADV.DELVRY03 for Outbound Idocs.
Can you check how much of the overhead information is actually "mandatory" on the sap side?
You can probably leave the information that you wont need.
You can find the detailed documentation (filed level) in WE60 transaction of sap.
Regards,
Ravi Kanth Talagana

ORI vs CHA qualifier in DELVRY or SHPMNT IDoc's

Similar Messages

Maybe you are looking for