Basic idoc shp_obdlv_save_replica02

hi experts,
i have an existing idoc shp_obdlv_save_replica02 in that idoc i have an segment called e2bpobdlvhdr for this segment i need to add a new feild... how we can do? please help me out with this... step by step by.... process i need.. dont give me a links... its not giving much idea...
regards,
anupama.p

Go to Transaction - WE30
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.
Linked the basic type: XXXXXX (Give the Basic Type which you are going to use)
and Provide description and enter.
Observe all the segments to be copied into your IDoc extension from linked basic type.
Select E1KNA11 and click on Create segment to obtain a popup window.
Provide the required values and observe child segment ZXXXXX to be added to
parent segment EXXXXX.
Release segment and IDoc extension.
Transaction: WE31
Segment type: ZXXXXXX
Path: Edit --> Set release
Assign Basic type to extension / messages
Transaction: WE82
Click on Change Icon then New Entries button
Select your XXXXX Message type against YYYYYY Basic type.
Reward if it is useful.
Thanks,
Srinivas

Similar Messages

Mapping Problem(file to 2 basic idocs)

Hi,
In my scenario sender File(divided into 3 parts) and receiver 2 basic IDOCS
I am having the conditions,
1) file field Trans_id(part-1 field) = 20 or 30 then only entire mapping required to transfer the file fields into SAP.(total scenario required to execute)
a)In that po_no( part-2 field) is coming from file then need to map part-2 fields of file to one idoc.
else need to map (file part1 and 2) fields to same IDOC-A
b)If all the fields of part-2 and part-3 equal then part-1 and part-2 fields to one IDOC-A and Part-3 fields to another IDOC-B.
which mapping is suggested to achive the requirement and procedure.
Thanks,
Praveen.

hi,
i Hope useful to you
/people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm - Walk through BPM
/people/siva.maranani/blog/2005/05/22/schedule-your-bpm - Schedule BPM
/people/sriram.vasudevan3/blog/2005/01/11/demonstrating-use-of-synchronous-asynchronous-bridge-to-integrate-synchronous-and-asynchronous-systems-using-ccbpm-in-sap-xi - Use of Synch - Asynch bridge
in ccBPM
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken] - Use of Synch - Asynch bridge
in ccBPM
Regards

Basic IDOC types

what are these ORDERS05, DELIVERY03 & WMMBID02
i found that these are basic idoc types. what does it mean?
Regards,
pandu.

Some IDoc types are supplied by SAP in the standard system,
these are the basic types. Other IDoc types are customer
extensions. In these cases, a basic type is combined with
an extension which is created by the customer, according to
certain rules. Unlike customer extensions , these extended
basic types are upward compatible.
regards,
srinivas
*reward for useful answers*

Find Idoc extension type for Basic Idoc type

Hi all,
Is there any way to find existing extesions for Idoc given by SAP? For example, for basic idoc DEBMAS05 for version 4.7 , Idoc extension is DEBMASEXT.
In similar way I want to know what is Idoc extension for Idoc basic type PREQCR02 [Create Purchase Requisition].
Thanks in advance.
Madhura

The reason is preqcr02 is a generated idoc type and matmas05 and debmas05 are not generated idoc types .
You can search in table EDBAS for this . If you go for dynamic debuggin , message comes from form
create_ext_structure in include MSED5F02
data: l_edbas type edbas.
select single * from edbas into l_edbas
     where idoctyp eq edi_iapi01-idoctyp.
if l_edbas-generated eq 'X'.
   message e099(b1) with
      'Action is not possible for generated idoctypes'.
endif.
Edited by: anil sasidharan on Feb 25, 2009 12:51 PM
Edited by: anil sasidharan on Feb 25, 2009 12:59 PM

Adding a segment to a Basic IDOC type

Hi every one,
How do i add a segment that I have created to an existing Basic Idoc type ?.
Can some one give me a solution for this.
Thanks,
Arul.

hi ,
Idoc extension can be done with 4 steps
1. creation of new extension type and a new segment
2. creation of a idoc type
3. link idoc type to message type
4. check the idoc type.
1. creation of new extension type and a new segment
we30--idoc typesobject name-extension type-create-create new-create-place the cursor on the location
2. step:
we30----
3. we82 or we 30
4. WEDI
If you find it useful plz mark the points
Regards,
Naveen

How to Create IDOCs for a Custom Basic IDOC Type

Hi friends,
I Have a Custom Basic IDOC Type.
For that IDOC Type i need to Create an IDOC for every Header Item.
The Header Item may have variation (Different) number of Line Items.
in this case can i Use
MASTER_IDOC_DISTRIBUTE and create the Idoc for each Header Item.
or is there any way to create the IDOCs
Thanks in Advance.
Ganesh.

Hi ,
If I am not wrong you need to pass data via fm "MASTER_IDOC_DISTRIBUTE".
So you can transfer row by row data into SDATA filed of structure type :EDID ,
by concatenating the data into one field of type sdata. and passing it into the fm.
I.e defining a internal table of type EDIDD.
Try this :
DATA : itab TYPE TABLE OF edid,
 itab1 TYPE TABLE OF edidc.
LOOP AT itab2 INTO wa_itab2.
CONCATENATE wa_itab2-t1 wa_itab2-t2 wa_itab2-t3 wa_itab2-t4 wa_itab2-t5
INTO result.
itab-sdata = result.
APPEND itab.
all function 'MASTER_IDOC_DISTRIBUTE'
 exporting
 master_idoc_control =itab1
OBJ_TYPE = ''
CHNUM = ''
 tables
 communication_idoc_control =
 master_idoc_data =itab.
EXCEPTIONS
ERROR_IN_IDOC_CONTROL = 1
ERROR_WRITING_IDOC_STATUS = 2
ERROR_IN_IDOC_DATA = 3
SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
OTHERS = 5
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.

Basic IDoc type ORDLGT01 is unknown

Hi All,
When I test run to execute business object from BUS2032 from SWO1,
I got the following message: "Basic IDoc type ORDLGT01 is unknown".
Please let me know why its so happening.
Regards
Bhaskar

PLEASE SEARCH SDN before posting ([rules of engagement|https://wiki.sdn.sap.com/wiki/display/HOME/RulesofEngagement])
[SAP Note 607330 ALE: Basic type ORDLGT01 unknown|http://service.sap.com/sap/support/notes/607330]

EDI 821 and EDI 823 field mapping file and basic IDOC type and message type

Hi All,
We are facing some issues regarding EDI 821 and EDI 823 file mappings.
We are mapping EDI 821 and EDI 823 transactions into SAP using IDOCs. Currently we are using the below entries
EDI 823 - Lock Box
Basic IDOC type - FINSTA01
Message type - FINSTA
Process Code - FINS
The problem is we are able to get the IDOC into SAP with status red and the various errors were due to not able to create the lockbox entry in SAP and once we got yellow status also but the lock box entry was not created and the errors are like No Conversions,no header etc.
EDI 821 -
Basic IDOC type - PEXR2002
Message type - PAYEXT OR REMADV
Process Code - PEXC OR REMA
We are facing the same problem here also and the internal payment order is not creating in SAP and IDOC was generated with yellow status and red status.
We are trying different combinations but nothing is working so far.
I need the following things to proceed furthur.
1)Are the IDOC , Message and process codes are correct that I am using now for both EDI 821 and EDI 823
2)If those are not correct, can you please let me know the correct entries
3) Please provide me the field mapping if any one of you have worked earlier for both the above IDOC and message type or new ones and we have one field mapping now but if you can send it to me then I can re check it.
4) Do we have to create any configuraion or customizing in SAP to create the IDOC in green status and if so please let me know the customizing steps and procedures for both EDI 821 and EDI 823.
thanks in advance for all your help.
Please let me know if my question is not clear.
Thanks,
Ramesh.

Hi Ramesh,
I believe you are using those interfaces with the business partner type as Bank, Whatever idoc type, message type and process code you have used are perfectly correct.
First of all did you enable your bank for EDI, the house bank has to be EDI enabled first then only your idoc's can be processed, talk to your fi functional consultant and he might help you.
Are you can give me the exact error and i can help you as well.
Thanks,
Mahesh.

I am receiving Basic Idoc Type error while I am executing SWO1 for BKPF

Hi
I am receiving Basic Idoc type error message while I am trying to test BKPF object. Please note that the Business Object is delegated to a custom BO. Can anyone tell me where the linkage is established between IDOC type and BO.
Thanks
Arghadip

Arghadip,
Can you check the transaction WE57?
Thanks

Restructuring the basic IDoc type DELVRY03

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

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

Basic IDOC Segment Enhancement

My requirement is to add a new segment to the basic IDOC structure
I have tried this using a Z 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.
Thanq

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.

Basic IDOC Structure Enhancement

My requirement is to add a new segment to the basic IDOC structure
I have tried this using a Z 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.
Thanq

My requirement is to add a new segment to the basic IDOC structure
I have tried this using a Z 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.
Thanq

Basic idoc type for asset creatioon and asset acquisition

Hi
Please can anybody tell me the basic IDOC type provided by SAP for
- Asset creation
- Asset acquisition.
Thanx in advance....

Hi,
Go through this link
http://www.sap-basis-abap.com/fico/configuration-in-asset-accounting.htm
help.sap.com/bestpractices/BBLibrary/documentation/B44_BB_ConfigGuide_EN_Nordics.doc
Reward points if found helpful...
Cheers,
Chandra Sekhar.

Diff between IDOC TYPE & Basic IDOC TYPE ?

what is the Diff between IDOC TYPE & Basic IDOC TYPE ?

Hi,
IDoc type contains basic IDoc type and extension.
Extension is a sub-object which extends an existing basic IDoc type. Extension types are not delivered by SAP. They can be created by the customer.
Regards,
Ferry Lianto

Hi gurus what is basic IDOC type

hi gurus what is basic IDOC type

Basic Type:
Basic IDoc type defines the structure and format of the business document that is to be exchanged between two systems.
Segments:
Segments form the basic building blocks of an IDoc type and are used to store the actual datta. A segment type is the name of a segment and is independent of the SAP elease. A segment definition is the release-specific name of a segment.
Steps in creating Segments:
T.Code WE31
Enter the name for your segment type and click on the create icon.
Type the Short text.
Enter the variable names and data elements.
Save and Go back.
Go to Edit -> Set Release.
Repeat the steps to create more segments.
IDOC TYPE:
Business data is exchanged with an external system using the IDoc Interface.
IDoc types (Special Structures) An IDoc type is defined through its permitted segments. Segments can be dependent on each other (parent and child segments). The IDoc interface can check for each IDoc whether thhe segments contained are compatible with thhe definitiion of its type. This systax check is activated or deactivated in the Partner Profiles.
Steps in creating IDoc Type:
T.Code WE30 to create IDoc Type.
Enter the Object Name, Select Basic Type and click Create Icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDoc name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press enter
The system transfers the name of the segment type to the IDoc editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation.
Save it and go back.
Go to Edit -> Set Release.
Message Type:
Steps in Creating Message Type:
T.Code WE81.
change the details from Display mode to Change mode
After selection, the system will give this message "The table is cross client (See help for further info)". Press enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back.
Assign Message Type to IDoc Type:
T.Code WE82
Change the details from Display mode to change mode.
After selection, the system will give this message "The table is cross client (See help for further info)". Press enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back.
Reward Points if useful.

Basic idoc shp_obdlv_save_replica02

Similar Messages

Maybe you are looking for