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

Similar Messages

Segment E1EDP36 not active in the DELFOR02 IDOC type.

Hi All,
I have been working with creating extensions for Idoc type DELFOR02 inn ECC 6.0. But for the basic idoc type DELFOR02 , the segment E1EDP36 is not active here.i.e., the idoc generated does not carry data for this particular segement.
This segment depends on entries in a structure xisautoeklwes ( include LEINMF3S, line 130). The underlying table for this structure would be ISAUTOEKLWES(Last Deliveries for FLAB).
Could anyone throw light on how this structure will be filled or how it has to be filled if I can make changes to the customer exit available there.
Thanks,
Savitha Patil

Hi Gearge,
To add custom segments, you should create an extension.
the TCODE is we30.
Refer this link:
http://help.sap.com/saphelp_erp2005/helpdata/en/dc/6b7d6243d711d1893e0000e8323c4f/frameset.htm
Regards,
Ravi

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.

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
<b>*reward for useful answers*</b>

IDoc type "DELVRY03" for INBOUND delivery confirmation and Outbound Deliver

Hi ,
We have a requirement where we have to send Inbound delivery confirmation as well as outbound delivery notification to our same customer. (3PL case)
We have a EDI partner who is receiving our messages and transforming them before sending it to customer.
Now my problem is , since I am using same idoc type (DELVRY03) for both cases therefore wondering how my EDI partner will differentiate whether received message is a INBOUND delivery confirmation or OUTBound delivery notification.
regards
Shrey

Thx for your reply ...
Wondering about the impacts , if I create a new message type like ZDESADV and attach it to DELVRY03.
In this i could have two message types DESADV and ZDESADV.
Will it impact anywhere ?
Regards
Shrey

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

Adding new segment to IDoc type DELVRY03

Hello everybody!
I just got a request to add two new segments to an Idoc (type DELVRY03) under the segment E1EDL24. (E1EDL43 and E1EDL41).
They told me to use the userexit EXIT_SAPLV55K_004 to add the new segments using the table IDOC_CONTROL since it is standard. But the problem is that the changes are not been saved.
I realised that by the time that this exit is called the standard already stored the information on EDID4.
I appreciate any help!
Thanks in advance!

Hi Kumar,
If we change EDBAS table data and modify my idoc type by adding segment.
after completing process have to move my object to production.
Hope it ll through an error... because it will check with table data also for validation.
could you please justify your answer kumar?
Thanks for your helpful information.
Regards,
BALAJI.

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 type ZSAB008 is unknown

We just completed a client copy of our Production landscape to our Test landscape including R/3, BW and SRM. In BW we have a source system of type File System that is used to upload data from flat files. Prior to the client copy uploads using this source system worked fine. Now when trying to upload a file I get the error above.
I manually created a source system of this same type in our Sandbox system to test this functionality prior to using in our "real" systems and I do not recall having to create any Idoc Types manually. I'm not sure how to fix this.
I'm looking at Source System > Restore but I can't find any good documentation to tell me if that is what I should do. Can someone tell me what "Restore" does and how the ZSABxxx Idoc types were created in the first place? In our BW SBX system we have 3 ZBASxxx types, one for each Source System, in BW TST we only have 2 one for the R/3 source system and one for the internal BW system. Are they automatically generated in the process of activating the Source System in the first place?
Thanks for your help.

Hi,
This is problem normally occurs,if you had not handled properly the system copy. Recently we also faced this problem . We solved it by the help of notes : 325470 and 184322
So Sit with Basis guy and use these notes.
With rgds,
Anil Kumar Sharma .P

RFC Error:The BW IDoc type ZSBA011 is not the same as the source system

Hi Experts,
RSA1Source System (Context Menu) Check
I am getting the below error
<b>The BW IDoc type ZSBA011 is not the same as the source system IDoc type ZSBD012               </b>
What might happened wrong.When i checked with my Basis Consultant who is new to job,Replied every this is ok with regeards to RFC.
Where should i check to correct the error
Thanks

Hi,
Did you do a system copy for BW ?
Try a restore (rightclick on your source system) in most cases this will solve the problem.
If not check the notes below:
184322 Procedure after DB copy of BW source systems
886102      System Landscape Copy for SAP BW 2.X, 3.X and NW2004s BI
325470      Activities after client copy in BW source systems
325525      Copying and renaming systems in a BW environment
184754      Procedure after BW database copy
184447      Building a BW-system landscape
184971      Notes on BW source system connections
140276      Error in source system assignment
524554      Storing destinations in the BW environment
538052 Maintenance of Myself destination in BW
Regards, Patrick Rieken
Message was edited by:
        Patrick Rieken - BI-Formance B.V.

Restructuring the basic IDoc type DELVRY03

Similar Messages

Maybe you are looking for