How to use E1BPPAREX - IDoc Segment enhancement

Hi,
can you provide me with some details on "how to use the E1BPPAREX" IDoc Segment ?
I want to enhance the standard PRICECATALOGUE02 IDoc with some customer defined fields.
There is a use of a STRUCTURE FIELD and 4 VALUEPARTS.
What kind of structure do i have to use ?
I red something about to enter 2 kind of structures ?
a) the first part = wrf_pricat_key*
b) second part = DDIC userdefined structure.
Thx,
Gordon

Hi Gordon,
1. Map customer data in E1BPPAREX segment fields:
STRUCTURE     CHAR     30     0     Structure name of BAPI table extension
VALUEPART1     CHAR     240     0     Data part of BAPI extension parameter
VALUEPART2     CHAR     240     0     Data part of BAPI extension parameter
VALUEPART3     CHAR     240     0     Data part of BAPI extension parameter
VALUEPART4     CHAR     240     0     Data part of BAPI extension parameter
2. Build a new implementationof BADI interface IF_EX_PRICAT_OUT_EXTIN (PRICAT_IN_EXTIN definition name) using SE19
3. Write the ABAP code for UPDATE_INBOUND_EXTENSIONIN method to manage your additional customer data:
UPDATE_INBOUND_EXTENSION: This method enables the data from the
ExtensionIn table parameter to be processed. This parameter may contain
customer-specific data that is either to be integrated into standard
tables in the price catalog, or stored in customer-defined tables.
BAPI_Table_Extensions are used for this integration into the standard
tables from the price catalog. These are enhancement concept objects for
BAPIs. SAP delivers them with the key elements, and customers enhance
them for their own fields in appends. The method receives the
Table_Extensions using the interface and then it can fill them. Once the
entries are returned after the method has been called, they are mixed
with the standard tables. If a customer wishes to update
customer-defined tables, a user-defined update module can be called in
the method and it will update the customer-defined tables.
When the method is called, the changing parameters are empty. They may
be filled in the method. They are used to provide customer-defined
fields in the standard tables. If entries are made in these structures
and tables, the 'entries_made' parameter must be set to 'X' so that the
entries are transferred from these structures and tables to the standard
tables in the price catalog. These parameters are BAPI table extensions.
These structures can be enhanced in the customer system with APPENDS.
This enhancement is exactly the same as the enhancement for the standard
tables involved. The customer-specific fields are transexported to the
standard tables after the method has been called using a
MOVE_CORRESPONDING. This involves the enhancement technology that
supports BAPIs in the standard system.
Reward points if useful.
Roger

Similar Messages

How to use STD IDOC WMMBID01

how to use Standard IDOC WMMBID01 for Posting Goods Receipts from External Systems in IM.

Hi,
Go through this link:[http://help.sap.com/saphelp_45b/helpdata/en/52/16aa5e543311d1891c0000e8322f96/frameset.htm]

How to identify/Highlight Idoc segment which is in error

Hi All,
We want that when the user looks at the IDoc which is in error, he should be able to find out the segment which is in arror. How to identify/Highlight Idoc segment which is in error.
Prashant

Hi kunyare,
If you are receiving errors when trying to restore your iPad from Recovery Mode, you may find the following article helpful:
Apple Support: Resolve specific iTunes update and restore errors
http://support.apple.com/kb/TS3694
Regards,
- Brenden

How to use standard IDOC - SHPMNT04

Hi Experts
Please help me out in IDOC's
I am new to IDOC's and i have to use SHPMNT04 IDOC .
Can any one help me from where i have to start and what to do ?
Thanks & Regards
Shaveta

hi, chk dis 4 basics of idoc.
IDOC is a intermidate documents:
An IDoc is a container that can be used to exchange data between any two processes. The document represented in an IDoc is independent of the complex structure used in SAP to store application data. This feature enables SAP to rearrange its internal structure without affecting the existing interfaces.
The word IDoc is used very loosely in the IDoc interface. An IDoc represents an IDoc type and IDoc data, depending on the context in which the word IDoc is used. An IDoc type defines the structure and format of the data being exchanged. For example, the IDoc type INVOIC01 defines the format of an invoice document. IDoc data can be seen as an instance of an IDoc type. For example, an actual invoice received from a vendor in electronic form is converted into an IDoc.
An IDoc is an instance of an IDoc type. Each IDoc is assigned a unique number for tracking and future reference. An IDoc serves as a focal object for tracking the state of the process that generated it.
The internal structure of an IDoc, showing the control record, data records, and status records
 One control record
 One or many data records
 One or many status records
 Control record. There is only one control record per IDoc. The control record contains all the control information about an IDoc, including the IDoc number, sender and receiver information, and other control information such as the message type it represents and IDoc type. The structure of the control record is the same for all IDocs and is defined by SAP. The field values, of course, can be different.
 Data record. An IDoc can contain multiple data records, as defined by the IDoc structure. Segments translate into data records. Data records store application data such as purchase order header information, purchase order details lines, and other relevant information.
 Status record. Multiple status records are usually attached to an IDoc. Status records are attached to an IDoc throughout the process as the IDoc achieves different milestones. A status code, date, and time are assigned at every milestone.
regs,
Hema.

How SAP handles Child Idoc segment data insertion automatically

Hello,
We have some Infotypes with extra segments and IDocs are getting created with Parent and child segments.
To fill the data into the parent/child segments, we are currently using User-Exits.
Is there any settings/config in table level(e.g. T777D etc), or any other way, so that SAP handles the data filling into parent/child segments automatically.
Thanks.

No I dont want to change the value in WE19.... In runtime I am changing the value of schedule Line quantity and the same is getting update in SDSA also but when a new idoc is getting created that value is not getting reflected in that Idoc segment field.
Kindly suggest.

How to change the IDOC segment data

How to change the segment data for all IDOCs at one shot J.
For exmple E1EDK02-QUALF - 004
                   E1EDK02-RGID - 100000008 (Inquiry No)
               to
       E1EDK02-QUALF - 004
                   E1EDK02-RGID - 200000005 (Quotation)
Any hints, tips.Appreciate your help and more rewards.
Regards,
Cris

Hi,
You can change the IDOC values using the transaction WE09
Give the IDOC number..
Press F8..
Expand the tree..
Double click on the segment..
Then in the menu..DATA RECORD -> DISPLAY/CHANGE..
It will go in change mode..Change the IDOC value..
Thanks,
Naren

How to use the Idoc number.(generated by prgram) and ALE

Hi All
I have a problem to use Idocs. I go thru the following steps but can not able to see the final output.
1.Create Segment ( WE31)
2.Create Idoc Type ( WE30 )
3.Create Message Type ( WE81 )
4.Assign Idoc Type to Message Type ( WE82 )
5.Make a report which gives us Idoc number.
Now my problem is where this Idoc number can we used .and how to relate this with ALE.
Regards
Manoj

Hi Manoj,
Use transaction code we02 or we05 to get the idoc no.
The table used are
EDIDC - Control record
EDID4 - Data record
EDIDS - Status record
Regards
Arun

How to use "Number of segments in a message" macro

When we export an EDIFACT document guideline file to Oracle 2.0 format, we have an option of enabling several macro nodes. One of them is "Number of segments in a message", which can be populate UNT+0074 element.
However, in transforming XML for an EDIFACT document, such as:
<ns0:Segment-UNT>
<ns0:Element-0074>###</ns0:Element-0074>
<ns0:Element-0062>MESSAGE_ID</ns0:Element-0062>
</ns0:Segment-UNT>
we do NOT know how to reference the "Number of segments in a message" macro. Currently we have to use a different approach.
We would highly appreciate if someone could enlighten us on using the macros.
We have searched all B2B documentations, and could not find any hints.
LXZ

Re: Segment SE - How to generate automatically for EDI_4010_850
Hope this helps

Basic IDOC Segment Enhancement

My requirement is to add a new segment to the basic IDOC structure
I have tried this using a <b>Z</b> type IDOC with reference to the basic type then i am getting an error saying that clipboard is empty.
Please help me to solve this.
<b>Thanq</b>

Dear Srikanth,
Extending a Basic Type
Prerequisites
You must have completed the required steps in Extending an IDoc Type .
It can occur that you want to fill table fields which already have an equivalent in the basic type but which are not supplied in the standard system. You therefore do not need to extend the basic type, but rather only the function module that supplies the application fields. In this case, skip the procedure.
Procedure
1. Choose SAP menu --> Tools --> IDoc Interface/ALE --> Development --> IDoc --> Generate ALE Interface --> IDoc Types (WE30). The IDoc type editor is displayed.
2. If you have not already done so, create a transport request for your development objects (extension segments, extension, function exit and so on). You can access the Workbench Organizer from the editor by selecting Requests (Organizer). From there, select Request ® Create and reply to the questions which appear on screen. By selecting you can return to the IDoc type editor.
3. Name your extension in accordance with the customer namespace and choose Extension as the development object. Choose .
The name of your extension should be no more than 8 characters if you wish to use the extension to communicate with partners who are using SAP Releases prior to 4.0. You can only use extension names with more than 8 characters from Release 4.0 onwards.
4. Choose one of the following options:
Create New: Create the extension without a reference.
· Create copy,which you can then change if necessary
· Create as successor: Note that only one successor is allowed per release for each extension.
5. Select the basic type which is to be combined with your extension. Confirm your entries.
The basic type is displayed as a tree structure. See the color legend (Utilities ® Color legend).
6. Position the cursor on the segment where you wish to append the extension segments (the reference segment). Choose . You must now assign attributes for these child segments:
· Mandatory segment (indicator): Must data be written to this segment in the IDoc?
· Maximum and minimum frequency of use:
7. You can add further children or grandchildren to this or any other reference segment in the basic type.
8. When the new extension is complete, you can save your entry.
You should keep the following factors in mind when dealing with extensions:
· Segments must not explicitly occur more than once in the IDoc type - this means that the extension cannot have any segments which already exist in the basic type. This also means that a successor must not have any segments which already exist in the predecessor.
· Parent segments of predecessors must remain parent segments in the case of successors.
· Extension segments cannot be created from reference segments using the Cut and Paste functions and vice versa.
In the example call your extension Z1ORDERS. Append Z1TEST1 child segment to E1EDP19reference segment in ORDERS01 basic type. The child segment can be used only once
Best Regards,
Rajesh
Please reward points if helpful.

How to use ale/idocs in sap crm to transfer master and transactional data

hi all,
I am working on sap crm7.0 ehp1. I want to transfer my master and transactional data from crm development system to crm quality system here through idocs. I am aware of basic ale settings and successfully transfe the ztable data through idocs. But i am not able to find any proper step by step procedure for maste and transactional data in sap crm. Also sap ecc tcode NACE is not available here.
pls help..
regards,
kavita chaudhary

Kavita,
In CRM, Exchange Interface (XIF) ALE/IDOC is available to transfer master and transaction data. You can go through the following link for set up.
Basic Data exchange set up for ALE IDocs - Wiki - SCN Wiki
You can extend the standard XIF IDOCs using Transaction BDFg as well.
Thanks,
Ravi

How to findout in IDOC whch segment error out

Hi All,
If an IDOC error out then how to know which IDOC segment needs to be corrected without going through all the segments. Is there any transaction or table exists to know the status of error segment.
Thanks in Advance
Swapna!

Hi,
There is no such transaction. Some time in WE02 it shows the errored data segment. To check if i shows the error segment or not,
- go to WE02 and display your errored idoc.
- from the menu select "Edit --> Segments with errors".
If it shows errored segments, you are lucky. Otherwise you will have to figure out which segments is with error.
Regards,
RS

How to assign idoc segment at runtime ??

Hi ,
I have a ztable which is maintained via sm30.
The field1 is a key field and other fields are idocsegment name , idoc field , field value .
Field1 = key field
idoc segment name (field2)
idoc field (field3)
field value(field4)
How do i update idoc segment and particular field with field4 at runtime .
segment name , field and value changes with the matching key field.
loop at it_edidd into wa_edidd
   where segnam = wa_ztable-idoc_segment.
wa_seg = wa_edidd-sdata.
how to assign the field at runtime ?????????????????????????
how to change the value of field ?????????????????????????
   update edid4 set   sdata = wa_seg
                      where docnum = wa_edidd-docnum
                      and   segnum = wa_edidd-segnum
                      and   segnam = wa_edidd-segnam.
   if sy-subrc <> 0 .
     rollback work .
     write: / wa_edidd-docnum .
   else.
     commit work.
   endif.
endloop.
Please help me with the above code .
Regards,
Rachel

Hello Rachel
You could do this the following way:
DATA: ls_edidd    TYPE edidd,
           ld_idx         TYPE i.
FIELD-SYMBOLS:
<ls_segment>         TYPE any,
<ld_field>                TYPE any.
LOOP AT it_edidd INTO ls_eddid
                             WHERE ( segnam = wa_ztable-idoc_segment ).
ld_idx = syst-tabix.
ASSIGN ls_edidd-sdata TO <ls_segment> CASTING TYPE (ls_edidd-segnam). " <<<
ASSIGN COMPONENT wa_ztable-field3 OF STRUCTURE <ls_segment>
                                  TO <ld_field>.
<ld_field> = wa_ztable-field4.
MODIFY it_edidd FROM ls_edidd INDEX ld_idx.
ENDLOOP.
However, be aware that your logic might fail in case of repetitive segments.
Regards
Uwe

How to chng the IDOC 1 package to other

Hi Friends,
How to change the IDOC SEGMENT from one package to other package.
Thanks & Regards,
Vallamuthu.M

Hi,
use Tcode - WE31 --developement segments..!
give your segment name and in change mode goto MENU->EDIT->Object Directory Entry..
U can able to change to already assigned package suppose say Z001 to Z111 here...!
hope try out this...!
Sasi Kanth.

Unable to release IDOC segment

Hello,
I have to add a new field to an existing Z IDOC segment. There were two versions existing with the same release 620, namely 000 & 001. My current system release is also 620 To Add a new field, I "cancel release" the latest version 001 . Then added a new field.
After adding the new field if I " set release", I get a error message "A released definition already exists for '620' in Release Z1ED..."
Does anyone know how to release the IDOC segment
Thanks

Hello Aravind,
I Have created one Segment type with some fields, changed the field length also its working.
just try to cancel the release and change the length of the filed and do it set release again.
Try it .
Thanks,
santhosh

How to use IDOC and RFC adapter in 1 scenario?

We have AAA field and BBB field and we want to send AAA field to receiver sap system using IDOC adapter and BBB field to receiver sap system using RFC adapter. But how to use IDOC and RFC adapter in 1 scenario and how to map and what are the design and configuration objects we require to create?

To achieve this you have to use
Two Interface Determinations
Two Communication Channels (IDOC & RFC)
& Two Receiver Aggrements.
Use the Enhanced Interface determination and give your conditions there. Based on you condition your interface mapping will be triggered and data will be sent to IDOC & RFC respectively.

How to use E1BPPAREX - IDoc Segment enhancement

Similar Messages

Maybe you are looking for