Extended IDOC for transaction VL02N : Error 51

Dear,
I am Working on Extended IDOC for transaction VL02N (Outbound Delivery) and stuck in Inbound with Error 51: Specifications for units and quantities contain errors VBPOK-MEINS TO LIPS-MEINS MT.
Message no. VL282
How to resolve it?
At Outbound Programmed at EXIT_SAPLV56K_002 and at Receiver did WE57, BD51, WE42, WE20 and using listed below programs.
Function Module - IDOC_INPUT_DELVRY      - SAP Standard
Function Type - F (Function Module)
Basic Type - DELVRY03      - SAP Standard
IDOC (Enhancement) - ZDELV - Custom
Message Type - ZDELVRY - Custom
Process Code      - DELV      - SAP Standard
Thanks-
Varun

Hi varun,
in SAP you have a few keys that not only have a description depending on language but also the key itself varies from language to language. You can see that if you double-click on a unit field like i.e. MARA-MEINS: On domain level it will show a conversion exit. If you try the conversion exit function modules, you will find out that i.e. PC english pieces will be mapped to internal ST wich comes from the german Stück which is the translation of pieces.
Be aware that this special logic may apply for document types, partner types and a few more (?).
So, in IDoc processing this may cause harm. I did not analyze DELVRY03 structure and processing, I don't know any of your data, I haven't seen any line of your code, I don't know what you actually implemented.
So now it is your turn to check what you pass in the unit fields and how this is handled.
Regards
Clemens

Similar Messages

BAPI or IDOC for transaction F-32

Hello everybody,
is there any bapi or IDOC for transaction F-32?
thanks,
Alejandro

Hi,
I'm not sure but I think the following's one can do the job :
BAPI_ACC_PYMNTBLK_UPDATE_POST
or
BAPI_ACC_BILLING_POST
I suggest you to take a look at the help,
Regards
Erwan.

Automatic transaciton posting for transaction VL02N

Hi Experts
        Can i know whats is the user exit for the transaction VL02N we want to use for the purpose of posting a transaction MIGO while save the outbound delivery document.
        My requirement is when save the delivery document in one plant, in other plant the goods receipt needs to be done against the purchase order mentioned in the sales order of the previous one.
     Pls advise me, Thanks in advance.
Regards
Rajaram

Hi,
Check user-exits for VL02N...
V50PSTAT               Delivery: Item Status Calculation
V50Q0001               Delivery Monitor: User Exits for Filling Display Fields
V50R0001               Collective processing for delivery creation
V50R0002               Collective processing for delivery creation
V50R0004               Calculation of Stock for POs for Shipping Due Date List
V50S0001               User Exits for Delivery Processing
V53C0001               Rough workload calculation in time per item
V53C0002               W&S: RWE enhancement - shipping material type/time slot
V53W0001               User exits for creating picking waves
VMDE0001               Shipping Interface: Error Handling - Inbound IDoc
VMDE0002               Shipping Interface: Message PICKSD (Picking, Outbound)
VMDE0003               Shipping Interface: Message SDPICK (Picking, Inbound)
VMDE0004               Shipping Interface: Message SDPACK (Packing, Inbound)
V02V0001               Sales area determination for stock transport order
V02V0002               User exit for storage location determination
V02V0003               User exit for gate + artl staging area determination (headr)
V02V0004               User Exit for Staging Area Determination (Item)
Reward points if useful....
Regards
AK

Userexit for extended idoc for std. idoc WMMBID02 for T.Code MB1A & MB1B

Hi,
Which userexit we have to use to populate values in to extended idoc fields of the standard inbound idoc WMMBID02?
Pls share ur experience.
Thanks & Regards,
Balaji

Hello using this you can find out used user exit
1.From SE93 get the program name corresponding to the transaction.
2. then se38 - > enter program name -> attribute -> display
3. Get the package from here.
4. Go to SMOD . Do f4 on enhancement -> information system. enter your package here
5. You will get the list of all the available exits for the package.
List could be a long one.Now best thing to do is to sit with your functional analyst. find out approproate exit from the description. put a break-point there. ask functional analyst to run the transaction. if transaction stops at the break point that's the exit you want

Create Outbound extended IDOC for venodr create & change (XK01 & XK02)

Dear all,
My requirement is as below:
I have to populate an extended IDOC of the standard IDOC CREMAS in the following cases.
1. When a new vendor is created from XK01 with classification characterstics value for supplier status as 'YES'.
2. When a vendor is changed by adding a partner function OA in the partner function.
3. We have to purposefully fail the IDOC when the partner function OA is deleted in XK02 transaction.
4. We have to purposefully fail the IDOC when the main vendor is blocked or deleted(XK05 or XK06).
Since i am new to IDOC, i tried many things but its not working.
I tried by the change pointer method for the standard IDOC but it will create the IDOC in all cases which we don't want it should be created only when supplier status is 'YES' and new partner function OA is created.
Regards,
Manjunath

hi,
I know how to extend an IDOC, but my question is after extending an IDOC i have to populate that outbound IDOC only in some cases.that is when a vendor is created with supplier status as YES, when a vendor is changed by adding an partner function.
I want these checks know where to make these checks before creating an outbound IDOC.i want to knaow a common point where i can make these checks like an exit.
i found 1 exit fo all the cases EXIT_SAPMF02K_001 but in this exit we will have the vendor number because it is exit before save.
Now i am looking into the FM 'MASTERIDOC_CREATE_CREMAS' in which we have an exit 'EXIT_SAPLKD01_001'.
Regards,
Manju

Clarifications in picklist output type EK00 for transaction VL02N

Hi evryone,
Can anyone please help me to generate a smartform for picklist output type EK00 for Tcode VL02N. In application V2 the standard program is RVADEK01 and the form SD_PICK_SINGLE,
what is the best way to create smartform and driver program , can I use the Standard Program or write the new driver program..
with regards,
Mittu

I dont think this is the right forum to post such question. This should have been posted in ABAP forum
thanks
G. Lakshmipathi

Extended Idoc for Purchase Order

Hi Gurus,
I have a requirement to extend a basic idoc type Orders. I know the process of creating a "z" segments and "z" idoc type but where should write the code to process the additional segments for ORDERS.
( FOR Master data i can find the Customer exit to process the "z" fields but i don't know where should i write the code to process the transactional data).
plz let me know u'r knowledge.........
Regards:
TMR.

check in orders out bound process code FM
there you can find the exit for the smae
Thanks and Regards
S.Janagar

Extended idoc for CREMAS04

Hi Friends,
I added custom segments to standard idoc CREMAS04 (i.e., I extended the Standard idoc CREMAS04).
I want to populate data to custom segments using standard transaction BD14(Send vendor).
Can you please suggest me what is the USER EXIT name for populating data to custom segments through transaction BD14.
Iam using message type as CREMAS
Bye
P.Kumar

Hello Praveen,
There is a BADI available for extending CREMAS: VENDOR_ADD_DATA_BI (as of 4.7) or in previous releases you can use enhancement VSV00001.
Regards,
John.

Extend Idoc INVOIC02 - E1EDKA1 - Syntax error

Hi All,
I have extended Basic idoc INVOIC02 and using exit EXIT_SAPLVEDF_002 to extend custom segment. I am trying to add a custom segment under E1EDKA1. In program I am inserting Z1 segment after parent segment E1EDKA1. I am passing Parent segment reference (INT_EDIDD-PSGNUM) and hierarchy level of custom (INT_EDIDD-HLEVEL) segment. Problem is custom segment still placed under root segment after E1EDKA1 segment, which is incorrect. Idoc error with status 26 Syntax error. Can any one tell me what I am doing wrong or how do I manage to get custom segment under parent segment E1EDKA1, so that I dont get this error. Below code for your reference. Thanks in advance.
Regards,
Tim
Program -
"ZXEDFU02" -
describe table INT_EDIDD lines gv_indes.
read table INT_EDIDD index gv_indes.
if sy-subrc eq 0.
if INT_EDIDD-segnam eq co_e1edka1 and
     INT_EDIDD-sdata+0(3) eq 'ZM'.
Now INSERT segment Idoc value and custom extend field
    if not gv_email is initial.
            INT_EDIDD-PSGNUM = gv_indes.
            INT_EDIDD-HLEVEL = '03'.
      move: co_z1edka1        to INT_EDIDD-SEGNAM,
            'email address'   to INT_EDIDD-SDATA.
      append INT_EDIDD.
    endif.
endif.
endif.

Your logic looks ok. I would remove the code to populate the parent segment number and hierarchy level. SAP will determine those on its own.
As for the result you are seeing, if there is a syntax error on an IDoc, the entire hierarchy will be lost so the fact that the custom segment is showing up at the same level as its parent doesn't mean that is actually causing the syntax error.
Did you add your extension in the partner profile?
Program -
"ZXEDFU02" -
describe table INT_EDIDD lines gv_indes.
read table INT_EDIDD index gv_indes.
if sy-subrc eq 0.
if INT_EDIDD-segnam eq co_e1edka1 and
INT_EDIDD-sdata+0(3) eq 'ZM'.
Now INSERT segment Idoc value and custom extend field
if not gv_email is initial.
INT_EDIDD-PSGNUM = gv_indes.
INT_EDIDD-HLEVEL = '03'.
move: co_z1edka1 to INT_EDIDD-SEGNAM,
'email address' to INT_EDIDD-SDATA.
append INT_EDIDD.
endif.
endif.
endif.

I am triggering My IDOC for XI interface Error passing data to port

Hi All
when i checked the partner profile , it is givng the error as this one , and i dont to how to go for this one
No Message Control entry for this entry

Hi Sridhar,
Cross check with this weblog:
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
Sachin

BDC for transaction AC02, error opening dataset returning 0.

Here is the code.
Help me ASAP..
<unreadable code removed by moderator>
Moderator message: please do some own research before posting, only posts text with less than 5000 characters, check formatting before posting, do not use terms like "ASAP".
Edited by: Thomas Zloch on Jan 13, 2012

open dataset                                                       *
FORM OPEN_DATASET USING P_DATASET.
OPEN DATASET P_DATASET
               FOR INPUT IN TEXT MODE
               ENCODING DEFAULT.
IF SY-SUBRC <> 0.
    WRITE: / TEXT-E00, SY-SUBRC.
    STOP.
ENDIF.
ENDFORM.
create batchinput session                                          *
(not for call transaction using...)                                *
FORM OPEN_GROUP.
IF SESSION = 'X'.
    SKIP.
    WRITE: /(20) 'Create group'(I01), GROUP.
    SKIP.
open batchinput group
    CALL FUNCTION 'BDC_OPEN_GROUP'
         EXPORTING CLIENT   = SY-MANDT
                    GROUP    = GROUP
                    USER     = USER
                    KEEP     = KEEP
                    HOLDDATE = HOLDDATE.
    WRITE: /(30) 'BDC_OPEN_GROUP'(I02),
            (12) 'returncode:'(I05),
                 SY-SUBRC.
ENDIF.
ENDFORM.
I'm using these performs because they appeared automatically when the recording became a program.

Extended Idoc - User exit for delivery VL01 and Invoice VF01

Hi Experts,
We are developing Extended Idoc for order - cash cycle.The extended Idoc contains 4 extra fields.
I want to know the User exits where i can populate the extended segment field values for VL01 and VF01 transactions.

HI
exits available for VL01.
VMDE0004                                Shipping Interface: Message SDPACK (Packing, Inbound)
VMDE0003                                Shipping Interface: Message SDPICK (Picking, Inbound)
VMDE0002                                Shipping Interface: Message PICKSD (Picking, Outbound)
VMDE0001                                Shipping Interface: Error Handling - Inbound IDoc
V53W0001                                User exits for creating picking waves
V53C0002                                W&S: RWE enhancement - shipping material type/time slot
V53C0001                                Rough workload calculation in time per item
V50S0001                                User Exits for Delivery Processing
V50R0004                                Calculation of Stock for POs for Shipping Due Date List
V50R0002                                Collective processing for delivery creation
V50R0001                                Collective processing for delivery creation
V50Q0001                                Delivery Monitor: User Exits for Filling Display Fields
V50PSTAT                                Delivery: Item Status Calculation
V02V0004                                User Exit for Staging Area Determination (Item)
V02V0003                                User exit for gate + matl staging area determination (headr)
V02V0002                                User exit for storage location determination
V02V0001                                Sales area determination for stock transport order
For VF01..
Enhancement
V61A0001                                Customer enhancement: Pricing
V60P0001                                Data provision for additional fields for display in lists
V60A0001                                Customer functions in the billing document
V05N0001                                User Exits for Printing Billing Docs. using POR Procedure
V05I0001                                User exits for billing index
SDVFX011                                Userexit for the komkcv- and kompcv-structures
SDVFX010                                User exit item table for the customer lines
SDVFX009                                Billing doc. processing KIDONO (payment reference number)
SDVFX008                                User exit: Processing of transfer structures SD-FI
SDVFX007                                User exit: Billing plan during transfer to Accounting
SDVFX006                                User exit tax line in transfer to accounting
SDVFX005                                User exit reserves in transfer to accounting
SDVFX004                                User exit G/L line in transfer to accounting
SDVFX003                                User exit cash clearing in transfer to accounting
SDVFX002                                User exit for A/R line in transfer to accounting
SDVFX001                                User exit header line in delivery to accounting
J_3RSINV

Problem creating extended IDOC

Hi Experts,
I am currently working on CRM 5.0. I need to create segment and attach it to the standard basic IDOC type CRMXIF_PARTNER_SAVE01. I am able to create segment in WE31 but i am unable to add that to the basic standard IDOC type.
It is displaying message "Action is not possible for generated idoc types".
Is there any other way to add this segment to the standard IDOC.
It will be great help if u can send me some documents on this...
Thanks,
Samm

Hi,
Create Extended IDOCe using transaction WE30.
-If u want to extend idoc type which already exists then use the radio button extension(where we can add few new fields
-After this click on create button as described above. It takes you to a popup screen where you fill the description and also select the radio button accordingly and say ok
-we go to next screen select idoc type and click on create new It gives a pop up window
-Once you are done with the addition save the IDOC type and release the idoc type
<b>Goto-> Edit -> Set release.</b>
This completes the creation of Ext IDOC type.
- Then assign this extension to the IDoc type in WE82.
<b>Reward with points if helpful.</b>
Regards,
Vijay

Extend idoc

for extended idoc i added the extended segment to basic type and doen
the code as per that but i would like to confirm one thing that for
every extended idoc for process code we need to modify the existing FM
like MASTERIDOC_CREATE_DEBMAS ,
for this FM we need to finc the enhansment and then modify the code
as per that , so is the same for all extended idoc we need to find
related FM for that and find enhancement and modify .

Enter transaction WE30 (ALE->Extension-> IDOC types->Maintain Idoc type)
- Type in your name of the extended IDOC type (usually starting with 'Z') and click on the Basic IDoc type, click the create icon.
- Click on Create new and enter a description and press enter.
- Click on ZIDOCTYPE01 and then on the Create icon.
- Enter ZIDOCTYPE as the segment type, click on Segment Editor.
- Enter a description for your segment type and create.
- Enter a description for your segment, enter each field required in your IDoc and press enter to validate.
- Save and generate, press back
- To release the segment choose Goto, Release from the menu.
- Check the box on the line of your segment.
- Save, back and enter.
- Your Idoc type structure should be displayed with your new segment.
- Save and back.
- To release the Idoc type choose Extras, Release type from the menu and Yes.
ALE FUNCTION MODULE ENHANCEMENTS
Having extended the IDOC type to contain additional fields for an inbound or outbound application, you now want to enhance ALE function modules for populating the additional segment on the outbound or applying the additional segment data on the inbound application.
The core working code for ALE processes for a given application area is always encapsulated in ABAP/4 function modules. These function modules are associated with such control information as message types and process codes. So the ALE process checks this control information and derives the name of the function module to invoke for that particular IDOC processing from certain database tables. These function modules contain objects known as customer functions, which can be considered SAP Enhanced user exits. A function module is called at a particular point during the processing of the main program or function module, and it can be used to influence data processing at that point by adding code to the customer function. The customer function behaves like a normal function module and has import and export parameters, tables (internal tables) statement, and exception processing. Unlike a conventional user exit, customer functions give you the ability to modify only data available to you by the function moduleâs parameters and internal tables. While most ALE/EDI function modules are supported by customer functions, there are ALE/EDI processes that still use conventional user exits. There are a few ways to determine which function module to enhance for a given message type/process code:
For master data distribution, from SALE go to Extensions -> Master data distribution -> Setup additional data for message types. Search for message type DEBMAS in this example. You see an entry for DEBMAS associated with function module MASTERIDOC_CREATE_SMD_DEBMAS. This data is stored on table TBDME. The function module names for all master data message types follow this pattern: MASTERIDOC_CREATE_SMD_messagetype. This function module calls another function module of name MASTERIDOC_CREATE_DEBMAS or MASTERIDOC_CREATE_messagetype. Search for the words customer function, and you find several hits that can be used to add code to the function module.
From WEDI got to Control -> Inbound process codes -> Inbound with ALE service -> Processing by function module (transaction WE42), or from WEDI go to Control -> Outbound process codes -> Outbound with ALE service -> With function module (transaction WE41). There will be function modules associated with the process codes. For inbound, the function modules usually follow this pattern: IDOC_INPUT_messagetype: for example, IDOC_INPUT_CHRMAS for inbound characteristics master.
Use transaction WE57 or from WEDI go to Development -> Message/Application Object. The entries list the function module, Business Object, message type, and IDOC type that are used for inbound ALE/EDI interfaces.
Customer functions are not specific only to ALE and EDI but also to all programs/modules in SAP R/3. Customer function is a SAP enhancement component; the other two types are menu and screen enhancements.
All customer function exits are maintained in SAP enhancements and are found by using transaction SMOD. After executing transaction SMOD, pull down (F4) on the enhancement name field, and execute again. This provides you with a list of all SAP enhancements available. SAP enhancements are grouped by development class pertaining to an application area. Choose Application development R/3 SD master data distribution for development class VSV to lead to a screen that lists VSV00001 as an enhancement (see Figure 5). Press Component +/- to display its function exit components. There are four possible components listed, all of which are function exits (and are function modules) that are called from the ALE function modules in the form Call Customer Function Î001â. This is a special occurrence of the ABAP statement Call. Go to item Exit_SAPLVV01_ 001, which you need to enhance for the Customer Master outbound example of an IDOC extension. In the ALE-function module MASTERIDOC_CREATE_DEBMAS, the statement CALL Customer Function 001 is translated in the background to call component EXIT_SAPLVV01_001. Although this function exit can be edited using transaction SE37, you will use a simpler approach.
When you use SAP enhancements and their components, you manage them with an SAP object known as a project, which is like an envelope containing the selected enhancements and their components. A project can be used to control the execution of components and to transport them to other clients and instances in SAP. Basically, the process involves creating a project, including enhancements and components that are to be enhanced, editing the components, and then activating the project. The following process creates a project for our example Customer Master IDOC extension:
Execute transaction CMOD.
Enter name of project, say CSTMAST1.
Click on Create.
Enter a description of the project.
Save.
Click on SAP Enhancements.
Enter VSV00001 for Enhancement.
Save.
Once youâve created the project, edit the function exit components and activate the project. Remember that the code in the function exit enhancement will execute only if the project is activated. In fact, this is a convenient SAP enhancements feature, whereby the work in progress (developing code in the customer function) will not affect users of that application. When the code is completed, the project can be activated so the enhanced functionality takes effect. It can also be deactivated for maintenance.
As mentioned earlier, customer functions (function exits) are embedded in ALE function modules and can be used to influence the creation and modification of IDOC data on an outbound application or to post additional or modified IDOC data to an inbound R/3 application. Function exits are similar to regular function modules, with import/export parameters, tables (internal tables), and exceptions.
The two important factors to consider while developing the customer function are:
1. The point in the ALE function module where the function exit occurs
2. The data made available by the customer function that can be modified or posted to the R/3 application, based on the direction.
Because some function modules have several customer functions, it is critical to choose the function exit best suited for that particular enhancement. Do not attempt to perform activities that the function exit is not designed for. The importance of this point is illustrated by the following description of enhancing function modules for outbound and inbound ALE interfaces.
Outbound interfaces. In an outbound ALE interface you use function exits (customer functions) to populate additional segments created by an IDOC extension or to modify the existing IDOC data segments as per business requirements. Previously, you identified that enhancement VSV00001 has a component EXIT_SAPLVV01_001 (function exit), which can be used for populating the additional data segment Z1SADRX that you created in the IDOC extension ZDEBMASX (IDOC type ZDEBMASZ, based on Basic IDOC type DEBMAS02). You also learned that the ALE function module that calls this function exit is MASTERIDOC_CREATE_DEBMAS, which has a statement Call Customer Function 001.
Browse the function module MASTERIDOC_CREATE_DEBMAS using transaction SE37. You will find that this customer function is invoked for every segment of IDOC type DEBMAS02. In fact, the function exit is called soon after the creation of an existing segment has been populated with data and appended to the IDOC data table (internal table). Also, the function exit is exporting the message type, IDOC type, and the segment name and is importing the IDOC extension type. It is also passing the IDOC data internal table. This indicates that the ALE function module is allowing you to populate additional segments for every existing segment and modify the existing segmentâs data.
Letâs write ABAP/4 code to accomplish the task of populating IDOC segment Z1SADRX with a contact personâs business address:
From SE37, display function module MASTERIDOC_CREATE_ DEBMAS.
Find Customer Function 001.
Double-click on 001.
The function EXIT_SAPLVV01_001 will be displayed.
Double-click on INCLUDE ZXVSVU01.
You will be asked to create a new include object. Proceed as desired.
Enter code (as in Listing 1).
Be sure to perform a main program check (Function Module -> Check -> main program) and extended program check (Function module -> Check -> Extended check).
Now that you have extended the IDOC and enhanced the ALE function module based on the requirements for the contact personâs business address on the Customer Master, letâs test the interface. You should create a logical system and define a port for this interface. You should also configure the Customer Distribution Model to indicate that message type DEBMAS is being distributed to this logical system. The only difference in configuration between a regular outbound ALE interface and an enhanced one is the partner profile definition. While maintaining the outbound parameters of the partner profile, make sure the IDOC type is ZDEBMASZ. The fields for Basic IDOC type and extension type are automatically populated with DEBMAS02 and ZDEBMASX, respectively.
To maintain the contact personâs business address of a customer:
Use transaction BD12 or from BALE go to Master Data ->Customer -> Send and send that Customer Master record by executing the transaction after filling in the relevant fields such as customer number, message type, and logical system.
Use transaction WE02 or WE05 to verify the IDOC created. You should see the new segment Z1SADRX populated with the correct data.
With SAP releases below 4.5B, you cannot capture changes to business address through change pointers because a change document object is not available for capturing business address changes, and also earlier releases have not been configured to write change documents for a contact personâs business address. If you would like this functionality, you can either create change document objects, generate function modules to create change documents, and perform ALE configuration to tie it in, or make a cosmetic change to the contact person screen data while changing the contact personâs business address so that it gets captured as a change to the Customer Master. Subsequently, the ALE enhancement that you performed captures the contact personâs business address.
Inbound interfaces. The process for enhancing inbound ALE interfaces is similar for outbound, with a few exceptions; specifically in the coding of customer functions (function exits) for the ALE/EDI function modules.
The first step is to create an IDOC extension for the specific Basic IDOC type by adding new segments at the appropriate hierarchy level: that is, associated to the relevant existing segment. Populate the data fields on the new segments with application data by the translator or external system/program before importing them into the R/3 System. Then, find the ALE function module that is invoked by the inbound processing. By browsing through the code or reading the documentation on the function exit enhancements using the SMOD transaction, identify the function exit in which you should place your code. The technique used in the code to post the additional or modified IDOC data to the application can vary based on the application rules and requirements, the data available at that point in processing, and the application function modules available to update the application tables. It is important to search first for application modules that process the data and see if they can be called within the function exit. If the additional data in the extended segments in specific to a custom table or resides in nonkey fields of a single or small set of tables, you may be able to update it directly by SQL statements in the function exit. This approach should be carefully evaluated and is certainly not highly recommended.
Another option is to use Call Transaction from within the function exit to process the additional data. For example, in the case of message type WMMBXY for inbound goods movements from a warehouse management system, the standard interface creates batches for materials, but does not update its characteristics. In such a case, you can use Call Transaction MSC1 to create the batch and assign characteristic values to it from within the function exit provided.
regards,
srinivas

How to extend idocs

hi gurus
      this is phaneendra i know how to extend the idoc
      ie we31, we30, we82,we57..........ie segment creation,
      adding it to basic idoc type and linking it
       but what exactly i want is coding for extended idoc
       in outbound and inbound ie in the customer exits what
       we have to write
can any body send me the code required for this in inbound and
in outbound dont send that present in arvind nagpal book that already i know
best regards
phaneendra punukollu
<removed_by_moderator>
Edited by: Julius Bussche on Jul 27, 2008 8:18 PM

Hi Phaneendra.
I would like to suggest a few references,
[SDN - Reference for Extending an existing IDOC|How to extend an existing IDOC!;
[SDN - Reference - Extending IDOC step by step|How to extend an IDOC step by step;
[SDN - Reference for populating segments of IDOC|How to populate IDOC segments...;
[SDN - Reference for Problem while Extending the HR IDOCS|Problem while Extending the HR IDOCS;
[SDN - Reference for Segments getting suppressed in Extended Idoc for Customer (change pointes) |Segments getting suppressed in Extended Idoc for Customer( change pointes);
[SDN - Reference for Setting attributes for segment types in IDOCS|Setting attributes for segment types in IDOCS;
Hope that's usefull.
Good Luck & Regards.
Harsh Dave

Extended IDOC for transaction VL02N : Error 51

Similar Messages

Maybe you are looking for