Inbound idocs segment fields

Hi,
Iam new to idocs and a functional consultant. I need to know whenever we receive the inbound idocs and if i see the segments of the inbound idoc, do the fields which i see in the segments are the sap fields.????/ for instance if the inbound idoc needs to create a sales order, then the fields of the segments of such an inbound idoc are the normal sap sales order fields ??
do i need to give functional specs to the abapers that whenever the inbound idocs is received the segments fields need to be mapped to sales order fields if such an idoc needs to create a sales order ??
regards
sachin

Hi Sachin,
Most of the IDoc segment fields are simmilar to SAP transaction fields e.g. most of the ORDERS IDoc segment fields will be simmilar to what you can see in VA01/VA02 screen fields.
Some fields may have different names.
In the case of few segments which may repeate in IDoc with different qualifiers (such as partner details, date segments), fields will be same but different qualifier value decides where these field values will be populated in the Order.
If you are using standard function module to create Order, it will take care of mapping IDoc segment fields to VA01/VA02 screen fields. But if it is a Z function module, then you need to specify the mapping.
Hope this information will help you.
Regards,
Mahesh Pakhale

Similar Messages

Replaced value is not getting relected in IDOC segment field

Hi,
Need your help for the below issue.
I am replacing the PO # with Delivery Doc # . But the replaced value is not getting reflected in the IDOC segment field(e1bp2017_gm_item_create-po_number.).
Function Module which I am using is IDOC_INPUT_MBGMCR as a copy.
Here is my code given below:
SELECT
            SINGLE vbeln
              INTO lx_vbeln
              FROM lips
             WHERE vgbel EQ e1bp2017_gm_item_create-po_number.
Move lx_vbeln TO e1bp2017_gm_item_create-po_number.
MOVE-CORRESPONDING e1bp2017_gm_item_create
               TO goodsmvt_item.
Then this is passed as TABLE in "BAPI_GOODSMVT_CREATE".
Please do the needful.

Hi Dheepa,
Check it in debug whether the filed is empty or having po#, when ur code is executed for the replacement. if it is empty, po# is populated after ur code. in this case you need to write the code in suitable place.
Reddy

How to map idoc segment field E1IDB02-FIIKONTO with BSEG-ESRNR.

Hi,
I have searched for lot of threads in the forum , and also i tried myself but i am not able to map this fields segment with my logic, so please anyone kindly contribute in mapping idoc segment field with the logic given below:
idoc type :PAYEXT outbound idoc.
message type: PEXR2002
This is my logic: i need to populate the ISR number(BSEG-ESRNR ) in idoc segment field( E1IDB02-FIIKONTO)
DATA : str1 TYPE string,
      len1 TYPE i,
      len2 TYPE i,
      str2 TYPE string,
      str3 TYPE string.
str1 = '01-1234-4'. ---> BSEG-ESRNR "ISR Subscriber Number
REPLACE FIRST OCCURRENCE OF '-' IN str1 WITH '_'.
REPLACE ALL OCCURRENCES OF '-' IN str1 WITH space.
CONDENSE str1.
len1 = STRLEN( str1 ).
IF len1 LT '9'.
len2 = '9' - len1.
CASE len2.
   WHEN '1'.
     REPLACE ALL OCCURRENCES OF '_' IN str1 WITH '00'.
   WHEN '2'.
     REPLACE ALL OCCURRENCES OF '_' IN str1 WITH '000'.
   WHEN '3'.
     REPLACE ALL OCCURRENCES OF '_' IN str1 WITH '0000'.
   WHEN '4'.
     REPLACE ALL OCCURRENCES OF '_' IN str1 WITH '000000'.
   WHEN OTHERS.
ENDCASE.
ELSEIF len1 EQ '9'.
REPLACE ALL OCCURRENCES OF '_' IN str1 WITH '0'.
ELSEIF len1 GT '9'.
REPLACE ALL OCCURRENCES OF '_' IN str1 WITH space.
CONDENSE str1.
ENDIF.
Thanks in Advance.

Resolved.

Idoc Segment Fields

Hi,
I am having a problem with the display of idoc segment fields. When i check the Idoc segment contents in WE02 it is displaying the fields which dont have the value in the DB table along with the fields which have the data. To avoid this what is the procedure. I dont want to display the fields in the content of segment which does not contains the data.
Plz help me out.
Regards
Santosh

Hi,
U have to use for reduced message type...U need to filter the segments which u don't want...In BD53 u need to create reduced message type....
plz go through the below link..
http://help.sap.com/saphelp_erp2005/helpdata/en/d3/06f6679aaf0e44b67ca6d6b58d91df/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a6702507d11d18ee90000e8366fc2/content.htm
Regards,
Nagaraj

Inbound Idoc - Date fields not getting saved

Hello,
I have created inbound idoc scenario in SAP. I receive Idoc from non SAP system to SAP system.
then data from IDoc is saved into different tables, for that I have written one function module (attached to process code)
One of the segments in IDoc type has date as a field. It is of type sy-datum.
When I receive Idoc in SAP only date fields are not getting saved in tables.
Is anything specific need to be done for date fields? please advice.

check which format you are getting into sap and make sure you are coverting in into required format.

Custom idoc segment fields not populated

Way back in 1999 someone create a custom Idoc type with custom Idoc segments in it. Unfortunately, they forgot to release one of the segments.
Recently a change was request to add new fields to this custom segment. In order to get the fields transported the segment had to be released.
All worked fine in Dev and the new Idoc segments were populated as expected. However when the idoc segment was moved to the test system all visually appears to be fine but when the idoc is created (status 50) the new fields are not popultated.
In 40B the start of the inbound process was IDOC_INBOUND_DATA. Does anyone know what the new starting point is in 4.7??
I beleive the error is actually that SData is not reading all the input values and stopping right where the old fields end in teh custom segment.
Thanks,
Anthony

additionally,
SAP will not allow us to release the basic idoc type because it was released in 40B. It also will not allow us to cancel the release since we are now in 620. So, unless anyone has input for this I think the only solution will be to create a successor IDoc type and change our apps to use the new IDoc type with it's enhancements.

Idoc segment field - maximum length ?

Hi,
what is the maximum of characters in a segment field of an idoc ?
regards,
Hans

Max length = 1000 characters
Check out
http://help.sap.com/saphelp_nw04/helpdata/en/1c/9fad3a05fdb92de10000000a114084/content.htm
FYI
ALE Interface
The following objects are generated from the application function module:
· Message, IDoc structure and segments: Mapping of the complex data type
· Outbound function module: Each IDoc always contains one application object only
· Inbound function module: IDocs are always transferred to the application individually or in packets of objects.
· Customizing objects required for the run
Assigning names to generated objects
· Default message (maximum 30 characters) proposed from the function module name.
· IDoc (maximum 30 characters) is derived from the message the last two characters are extended by 01 (message <= 28 characters) or are replaced by 01 (message > 28 characters).
· Generated function module name
Outbound (maximum 30 characters): ALE_function module name (default)
Inbound (maximum 30 characters): IDOC_INPUT_message (default)
· Segments
The default segment name begins with E1 for SAP and Z1 for customers, or namespace /.../. A meaningful and unique segment name is assigned as follows:
- In the application system (maximum 27 characters):
The segment name is derived from the structure name:
· If the structure name is shorter than 24 characters, the segment name is copied directly.
· If the structure name is longer than 23 characters, it is shortened to 23 and the less important characters at the front are cut off. The remaining characters are used to form a number that establishes the uniqueness of the shortened name. If numbers 01 to 99 are used, assignment continues with numbers 100 to 999 until the segment name becomes unique. This ensures that new segment names are created for the same structure, when this structure is used many times in a complex data type.
Hope thisll give you idea!!
P.S award the points.
Good luck
Thanks
Saquib Khan
"Some are wise and some are otherwise"

How to Read Idoc - Segment fields values and status messages

Hi,
I am having one requirement as i want to read the segments along with the field values and also i want to read all the status messages.
first i read the idoc data from EDIDS and segments data from EDID4 and the staus messges from T100. but still i am not getting all the status messages.
is there any other table which contains the information of IDOC segments and field values and also the status messages.
Regards,
Kumar

You need to use
V_MSGNO = EDIDS-STAMNO.
CALL FUNCTION 'MESSAGE_PREPARE'
EXPORTING
    MSG_ID   = EDIDS-STAMID
    MSG_NO   = V_MSGNO
    MSG_VAR1 = EDIDS-STAPA1
    MSG_VAR2 = EDIDS-STAPA2
    MSG_VAR3 = EDIDS-STAPA3
    MSG_VAR4 = EDIDS-STAPA4
IMPORTING
    MSG_TEXT = V_TEXT.
WRITE: / V_TEXT.
a®

Idoc segment field length changes

Hi friends,,
I am new to idoc.
My requirement is in my segment
i am having 5 fields and also this segment is already realeased one.
i wnat to change the field length from 10 to 20 . how to do this ?
actually what i did is
1. i cancel the release for that segment.
2. in that field inside the dataelement i changed the field length from 10 to 20.
3. data elemnt get chaged from 10 to 20 but Export length for that field in Idoc segment still retain the 10 only
can you plz how to resolve this
deva

Hi,
The way you used is right. ( cancel release or create a new segment )
After you cancel release, try delete that field, and insert a new one.
If it isn't valid still, create a new segment instead.
Regards
Sam

Inbound Idoc segment change

Hi All,
How can We modify or append a segment to the inbound IDOC. The scenario is as follow
We have an inbound IDOC to create/change contract order. There are some segments in the IDOC to hold the error records.
while processing the inbound IDOC we need to fill these blank segments with relevant data, so that we can reprocess the IDOC with ease.
I am trying the modify the IDOC_DATA inside the processing function module. Till the end of the function module IDOC_DATA is having the added segment data, however when I am checking from WE02, the segments are appearing to be blank.
Please let me know, what is missing above.
Thanks & Regards
D. Pradhan

Which exit / BAdI are yous using for adding the segment & what is your inbound processing function module ?
Anyways i also had the same problem a few weeks back i was trying to delete a segement though
My understanding is in WE02 it displays the data from EDIDC & EDIDD. In your I/B processing FM you only modify the data in the IDOC_DATA table & not in EDIDD.
Check in EDIDD, the segment would not be there.
BR,
Suhas

** Inbound IDoc - One field is missing but it is displayed in SXI_MONITOR

Hi Friends,
We have developed IDoc to IDoc scenario. Source IDoc is sent from 3rd party system. Target is an Z IDoc (Replica of VEHCLE01 IDoc).
When we test the source IDoc XML from RWB, the message processed successfully in SXI_MONITOR and target IDoc is also created in backend SAP system. But, the problem is that, in target payload there are 5 fields. But, in the physical idoc created in SAP system has only 4 fields. The last field is missing.
Since it is inbound IDoc, I deleted the IDoc meta data in IDX2 txn, and reimported again the Z IDoc. But, again the same problem is coming. i.e one field is missing in inbound IDoc. But, in the receiver payload, that field is there with value.
Kindly clarify, friends.
Kind Regards,
Jegathees P.

HI,
If that field is missing for first time in R3 means(ie Receiver system, Idoc posting in we02) , then
XI side:
1. u have check whether that field is existing in Target Interface,Target Message in Interface Mapping
2. Make sure that u have mapped that field in Message Mapping.
R3 (receiver side)
1. Plz check we30 , whether that field is there for that ZIdoc structure
2. Take the same Idoc which got posted , test in we19 whether that Idoc getting posted with that field or not?
check whether ur Idoc structure is activated in XI
Thanks
Praba

IDOC segment fields prefixing blank space with values

Hi Experts,
I am sending data through custom IDOC from SAP to XML which generates successfully but getting 2 problems in the data.
its having 3 level idoc segments:
SEGMENT1 with 1 field (field_name(20))
SEGMENT2 with 3 fields, (code_g(20), field_name(20), value(20))
SEGMENT3 with 4 fields, (code(20), field_name(20), Language(2) & text(20))
When i check the idoc in WE02,
1. i found that segment2-value field is prefixing some space along with the values.
    Eg: if the output is "0111" whihc is plant, in the output (WE02) it is giving "       0111"
2. Segment3-language is no where in the output and text which should come as "011" is coming like "       EN011" means it is concatinating language field value and displaying it with the text field value with prefixing space.
This is happening in PRD not in QA & DEV. I also checked the transport req and everything, Its same everywhere.
Can anyone please help me on this.
Regards,
Nik

Hi,
This issue happnes when u are moving the data to iDOC segement with offset.
to aviod this improper move instead of using offset statement use below mentioned code.
decalare a structure as
Data SEG1 type SEGMENT1 ,
        SEG2 type SEGMENT2,
       SEG3 type SEGMENT3.
then while moving
SEG2-code_g = 'XXXX'
SEG2-field_name = 'YYYY'
SEG3-value = 'ZZZZ'
here u are moving the segment values to idoc data (SDATA) and then append it.
move seg3 to idoc-sdata.
then append it to idoc.
hope this helps

Value for IDoc Segment field SEGMENT

Hello,
In the Integration Repository, while creating Message Mapping between a flat file (inbound) & an IDoc (outbound), I'm getting an error that not all target fields are mapped. In the target structure (IDoc), each segment has a field named SEGMENT. Can someone please tell me what value should go here. These are not part of the IDoc but seem to be a requirement in XI message mapping.
There is also a segment called BEGIN (Type - xsd:string) which is defined as required. Please write as to what should be populated in this segment.
Any help is greatly appreciated.
Thanx in advance.
Homiar.

My current scenario is
File Adapter -
> XI -
> SAP R/3 (Idoc Adapter).
I will be using FIDCPP2 IDOC.
1. For an instance following is the structure, in this case how can I achieve getting a set of data in one IDOC and another set in other IDOC based on document no.
CC Doc No. line items
UK01 456 1
UK01 456 2 -
> IDOC 1
UK03 456 3
UK04 450 1
UK04 450 2 -
> IDOC 2
UK04 450 3
i). Is there any way to create instances of idocs in XI or any alternative way out.
ii). Where/ how can I give the condition, that based on Document No. should create another IDOC instance.

Suggest a TABLE CONTAINING THESE IDOC segment FIELDS

E1MBXYJ : Create Goods Movement from Non-SAP System: Item++
Segment definition E2MBXYJ001 Released since Release 620 , Segment length: 0476
For the following fields. Tell me a table which contains a majority or all of the below fields.
PARGB : Trading partner's business area
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 001, Offset : 0063. external length : 000004
PARBU : Clearing company code
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 002, Offset : 0067. external length : 000004
CLASS : Class number
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 003, Offset : 0071. external length : 000018
UMCLA : Class number
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 004, Offset : 0089. external length : 000018
XCLAS : Checkbox
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 005, Offset : 0107. external length : 000001
UMXCL : Checkbox
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 006, Offset : 0108. external length : 000001
XNIBU : Checkbox
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 007, Offset : 0109. external length : 000001
BDTER : Requirement Date for the Component
internal data type : DATS
Internal length : 000008 characters
Position in segment : 008, Offset : 0110. external length : 000008
TBBEL : Article doc. no. of transfer requirement to be cancelled
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 009, Offset : 0118. external length : 000010
TBBPO : Article doc. item of transf.reqmnt item to be cancelled
internal data type : NUMC
Internal length : 000004 characters
Position in segment : 010, Offset : 0128. external length : 000004
TBBJR : Article doc. year of transfer requirement to be cancelled
internal data type : NUMC
Internal length : 000004 characters
Position in segment : 011, Offset : 0132. external length : 000004
OBJNR : Object number
internal data type : CHAR
Internal length : 000022 characters
Position in segment : 012, Offset : 0136. external length : 000022
AUTYP : Order category
internal data type : NUMC
Internal length : 000002 characters
Position in segment : 013, Offset : 0158. external length : 000002
QPLOA : Inspection Lot on Which the Usage Decision is Based
internal data type : NUMC
Internal length : 000012 characters
Position in segment : 014, Offset : 0160. external length : 000012
TBPKZ : Indicator: No Transfer Requirement Created
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 015, Offset : 0172. external length : 000001
TAFKZ : Indicator: do not cal up automatic TO creation
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 016, Offset : 0173. external length : 000001
KZEAR_OLD : Final Issue for This Reservation
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 017, Offset : 0174. external length : 000001
RSART : Record type
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 018, Offset : 0175. external length : 000001
PPRCTR : Partner Profit Center
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 019, Offset : 0176. external length : 000010
XMEVO : Propose quantities
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 020, Offset : 0186. external length : 000001
UMLGT : Storage Type
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 021, Offset : 0187. external length : 000003
UMLGP : Storage Bin
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 022, Offset : 0190. external length : 000010
MENGE : Quantity
internal data type : QUAN
Internal length : 000013 characters
000003 decimal places, without sign
Position in segment : 023, Offset : 0200. external length : 000015
MEINS : Base Unit of Measure
internal data type : UNIT
Internal length : 000003 characters
Position in segment : 024, Offset : 0215. external length : 000003
FKBER : Functional Area
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 025, Offset : 0218. external length : 000004
MHDAT : SLED/Best-Before Date or Date of Production
internal data type : DATS
Internal length : 000008 characters
Position in segment : 026, Offset : 0222. external length : 000008
BSSKZ : Special movement indicator for warehouse management
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 027, Offset : 0230. external length : 000001
EXIDV : External Handling Unit Identification
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 028, Offset : 0231. external length : 000020
BERKZ : Material Staging Indicator for Production Supply
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 029, Offset : 0251. external length : 000001
PRVBE : Supply Area
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 030, Offset : 0252. external length : 000010
KZECH : Determination of batch entry in the production/process order
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 031, Offset : 0262. external length : 000001
UPTYP : Subitem Category, Purchasing Document
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 032, Offset : 0263. external length : 000001
REFIX : Field defined as in SY-TABIX
internal data type : INT4
Internal length : 000010 characters
Position in segment : 033, Offset : 0264. external length : 000011
VLIEF_AVIS : Delivery
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 034, Offset : 0275. external length : 000010
VBELP_AVIS : Delivery Item
internal data type : NUMC
Internal length : 000006 characters
Position in segment : 035, Offset : 0285. external length : 000006
XWAIT : Checkbox
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 036, Offset : 0291. external length : 000001
XNOEQ : Checkbox
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 037, Offset : 0292. external length : 000001
ILINR : IDoc line item number
internal data type : NUMC
Internal length : 000006 characters
Position in segment : 038, Offset : 0293. external length : 000006
VOLUM : Volume
internal data type : QUAN
Internal length : 000015 characters
000003 decimal places, without sign
Position in segment : 039, Offset : 0299. external length : 000017
VOLEH : Volume unit
internal data type : UNIT
Internal length : 000003 characters
Position in segment : 040, Offset : 0316. external length : 000003
ANZL1 : Number of Storage Units to be Placed Into Storage
internal data type : DEC
Internal length : 000003 characters
No decimal places, without sign
Position in segment : 041, Offset : 0319. external length : 000004
ANZL2 : Number of Storage Units to be Placed Into Storage
internal data type : DEC
Internal length : 000003 characters
No decimal places, without sign
Position in segment : 042, Offset : 0323. external length : 000004
LMEN1 : Quantity per Storage Unit to be Placed into Stock in Alt.UoM
internal data type : QUAN
Internal length : 000013 characters
000003 decimal places, without sign
Position in segment : 043, Offset : 0327. external length : 000015
LMEN2 : Quantity per Storage Unit to be Placed into Stock in Alt.UoM
internal data type : QUAN
Internal length : 000013 characters
000003 decimal places, without sign
Position in segment : 044, Offset : 0342. external length : 000015
LETY1 : Storage Unit Type
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 045, Offset : 0357. external length : 000003
LETY2 : Storage Unit Type
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 046, Offset : 0360. external length : 000003
KZKUB : Indicator: Do not create posting change notice
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 047, Offset : 0363. external length : 000001
UBTYP : Storage Type
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 048, Offset : 0364. external length : 000003
UBLGP : Storage Bin
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 049, Offset : 0367. external length : 000010
MBLNR : Number of Article Document
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 050, Offset : 0377. external length : 000010
MBLPO : Item in Article Document
internal data type : NUMC
Internal length : 000004 characters
Position in segment : 051, Offset : 0387. external length : 000004
MJAHR : Article Document Year
internal data type : NUMC
Internal length : 000004 characters
Position in segment : 052, Offset : 0391. external length : 000004
URZEI : Original line in article document
internal data type : NUMC
Internal length : 000004 characters
Position in segment : 053, Offset : 0395. external length : 000004
GEBER : Fund
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 054, Offset : 0399. external length : 000010
FISTL : Funds Center
internal data type : CHAR
Internal length : 000016 characters
Position in segment : 055, Offset : 0409. external length : 000016
KZBWS : Valuation of Special Stock
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 056, Offset : 0425. external length : 000001
KDAUF_SD : Sales Order Number
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 057, Offset : 0426. external length : 000010
KDPOS_SD : Item Number in Sales Order
internal data type : NUMC
Internal length : 000006 characters
Position in segment : 058, Offset : 0436. external length : 000006
XRERE : Reservation reading is mandatory
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 059, Offset : 0442. external length : 000001
XSTOR : Reverse posting indicator
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 060, Offset : 0443. external length : 000001
BRGEW : Gross weight
internal data type : QUAN
Internal length : 000015 characters
000003 decimal places, without sign
Position in segment : 061, Offset : 0444. external length : 000017
GEWEI : Weight Unit
internal data type : UNIT
Internal length : 000003 characters
Position in segment : 062, Offset : 0461. external length : 000003
WM_KZBEW : Movement Indicator
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 063, Offset : 0464. external length : 000001
WENUM : Goods Receipt Number
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 064, Offset : 0465. external length : 000010
GEBEH : Lot Container
internal data type : UNIT
Internal length : 000003 characters
Position in segment : 065, Offset : 0475. external length : 000003
ANZGEB : QM - No. of Containers
internal data type : QUAN
Internal length : 000006 characters
000003 decimal places, without sign
Position in segment : 066, Offset : 0478. external length : 000009
KANBA : Kanban Indicator
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 067, Offset : 0487. external length : 000001
BSTMG : Goods receipt quantity in order unit
internal data type : QUAN
Internal length : 000013 characters
000003 decimal places, without sign
Position in segment : 068, Offset : 0488. external length : 000015
FUNC_AREA_LONG : Functional Area
internal data type : CHAR
Internal length : 000016 characters
Position in segment : 069, Offset : 0503. external length : 000016
GRANT_NBR : Grant
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 070, Offset : 0519. external length : 000020

see the tables MSEG, MKPF.
REgards,
Ravi

To remove leading zeroes and take directly from IDOC(Segment field) to file

Hi SapAll.
i have got a simple requirement in a idoc to file Interface.
here in a sender Idoc there will be one segment with one field,the requirement is to remove leading zeroes and take directly the data from this field and map to one of the field in reciever file structure.
i had used the formatnumber (under arithmatic functions)in PI 3.0 but now when iam using it in PI7.1 it was raising some jave exception error.
it would be preferable if any body can give me the solution without user defined functions.
regards.
Varma.

from your first post:
i had used the formatnumber (under arithmatic functions)in PI 3.0 but now when iam using it in PI7.1 it was raising some jave exception error.
use the same formatting that you used in 3.0 .... try with just a # in the FormatNum function.
Regards,
Abhishek.

Inbound idocs segment fields

Similar Messages

Maybe you are looking for