Vendor Address in IMessage type ORDERS basic type ORDERS01

The idoc has three such segments E1EDKA1 AG: E1EDKA1 LF : E1EDKA1: WE. The segment E1EDKA1 LF shows the partner number but does not bring in the vendor address. What are we missing..please guide?
Thanks

Check if the address fields have been mapped
1) Go to transaction WE30.
2) Give the object name as ORDERS01
3) Click on Display(F7)
4) It will display the list of segments used for the IDoc
5) Click on any segment and click on Segment Editor (F5)
6) It will display the field names
reward points if it helps
regards
Biju

Similar Messages

What is the message type and basic type used for catsdb in idoc help me

what is the message type and basic type used for catsdb in idoc help me
ANY IDOC FOR CATSDB PLEASE TELL,
Regards,
Jagrut BharatKumar Shukla
points will be awarded

Hi,
Check these message types.
ATT_ABS_WITH_COST and WORKSCHED_WITH_COST.

Inbound idoc mess type:DESADV basic type: DELVRY03 Item text

Hi all,
W're having a inbound process to create inbound deliveries via IDOC.
mess type:DESADV basic type: DELVRY03
We want to create a item text on the delivery via the IDOC. Is this possible?
I see that there's a segment E1TXTH9 - E1TXTP9 to put in texts.
But as I see it, to create a text, we have to give the delivery nr in TDOBJECT TDOBNAME TDID TDSPRAS LANGUA_ISO.
But since we are creating it, this is not possible.
Is there any way to create an item text on an inbound delivery via the IDOC? And how.
Thanks a lot!
Caroline,

Hi Chris,
Before end of the ur functiond module (Idoc_input_xxxxxxx) create an Enhnacement spot . at this point I hope so delivey will be created already .so now u can get the delivery number
**********The Logic for Text Field filling*******************
IF NOT vbeln IS INITIAL.
DATA : L_FNAME TYPE THEAD-TDNAME,
 L_FID TYPE THEAD-TDID,
 IT_TLINE TYPE TABLE OF TLINE,
 WA_TLINE LIKE LINE OF IT_TLINE.
CONSTANTS :C_FID TYPE THEAD-TDID VALUE '0004',
 C_FID1 TYPE THEAD-TDID VALUE '0007',
 c_Text(40) type c value 'xxxxxxxxx',
 C_LANG TYPE THEAD-TDSPRAS value 'E',
 C_FOBJECT TYPE THEAD-TDOBJECT VALUE 'BELEG',
 C_FFORMAT TYPE TLINE-TDFORMAT VALUE '*'.
Reading the Idoc data table for Text field population
 READ TABLE IDOC_dATA INTO IS_EDIDD
 WITH KEY SEGNAM = c_segnam_e1edkt2.
 MOVE IS_EDIDD-SDATA TO IS_E1EDKT2.
 CONCATENATE mrm_RBKPV-BUKRS mrm_BELNR mrm_GJAHR INTO L_FNAME.
 if sy-subrc = 0.
 MOVE: IS_E1EDKT2-TDLINE TO WA_TLINE-TDLINE,
 C_FFORMAT TO WA_TLINE-TDFORMAT.
 APPEND WA_TLINE TO IT_TLINE.
 CALL FUNCTION 'CREATE_TEXT'
 EXPORTING
 fid = c_FID
 flanguage = C_LANG
 fname = L_FNAME
 fobject = C_FOBJECT
 SAVE_DIRECT = C_X
 FFORMAT = C_FFORMAT
 tables
 flines = IT_TLINE
 EXCEPTIONS
 NO_INIT = 1
 NO_SAVE = 2
 OTHERS = 3
 IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 ENDIF.
I hope it resolves ur problem.Please let me know if u have any
Queries.
Rgds
Sree m

I want the message types and basic types for catsdb table

i want the message types and basic types for catsdb table

Hi Jagrut,
Message Class is "LR".
Reward points, if helpful.
Regards,
Atin

IDOC question on Message type and Basic Type - Partner Profile

Hi all,
I am wonder if I can post any IDoc question in this right forum/module. If not please direct me to the right forum/module. I am a newbie in IDOC setup.
My question is about the setup of Partner Profile creation (WE20).
When creating a new partner, for example with partner type LI, I notice there is outbound parameter and inbound parameter.
Questions:
1 u2013 It makes sense to have only one message type record appear in EITHER one of these two tables. I notice that some partner in my system has message type record exist on both the inbound and outbound parameters table, why system allows? What is the business rational?
2 u2013 May I have a list of standard SAPu2019s Message Type object of its usage description, and its allowable Basic Type (ie. IDOC TYPE). Basically a website to describe their (i.e. Message type and its Basic Type) business usage.
Thanks.
tuff

Tuff,
Below are my thoughts,
There is a partner sing partner type LI. This partner in the WE20, has one record (i.e. with Message Type ORDERS) exist in the Outbound Parameter table. This partner also has 4 records (i.w. with Message Type DESADV, INVOIC, MBGMCR, and ORDRSP) exist in the Inbound Parameter table. So my question is what is the business rational behind this kind of setup. Because I am confuse when come to create a partner profile, whether I need to create a message type in Inbound Parameter table or Outbound Parameter table, or I need both.
OK, so looking at the above example, you have an orders message type(This is for creating an order) in the outbound, this means that you are sending out an IDOC(purchase order for ex) to this partner, so that this partner can create an SO in his system and fulfill your order.
Now you also, mention that you have other four Message types for the same partner on the inbound, now let us look at the above scenario, you have asked your partner to fulfill the order, i guess you would like to get a confirmation from him/her if the order was created or not in his/her system and how and when is he/she going to fulfill your order requirement. This he/she does by sending an response to your order - ORDRSP.
And when the partner is ready to ship your order to you, he/she sends out a Advance Shipping Notice - ASN via the IDOC of message type DESADV.
Finally and most importantly , he/she will send you the invoice - INVOIC for the order.
In general, you interact with your partner via Business Docs - Order, Delivery, ASN, Invoice etc, so whatever document come from your partner - ORDRSP, INVOIC etc will be on the inbound profile of the partner. Whatever docs that you send ORDERS, ORDCHG etc etc will be on the outbound profile of the partner.
2 - Bascially I would like a reference in any website that allow me to choose which message type is best use for my partner profile, so that I don't have to reinvent.
Well, there is no choice of choosing/best message type for a given requirement - So for sending an Invoice the message type is INVOIC, ORDERS - For order creation, ORDCHG for order change etc. However the IDOC type, is some thing that you can choose, for Ex: ORDERS01 - ORDERS05, these are the IDOC types that are available, so if you are interacting with a partner who are running an old version of SAP and their system has only upto ORDERS02 in their version of SAP then you would use ORDERS02.
Regards,
Chen

Prevent changes to ship-to and vendor address in Process Purchase Orders

Hi SRM experts,
I have recently used BBP_UI_CONTROL_BADI to affect the displays of fields and buttons in the shopping cart. I now need to change the displayed fields in the Process Purchase Order screens (Vendor Address and Ship-To address) to prevent edit. I've debugged in method BBP_PO_UI_CTRL and see screens 1000, 2200... 3000 etc. but can't see the screens and fields I need to affect. I suspect that I might be at the limitation of using the BADI or am I looking in the wrong place?
Can anyone help?

Hey,
i believe you have filter for shopping cart (BUS2121) in BBP_UI_CONTROL_BADI. you need to do a seperate implementation for PO (BUS2201), Which should/must work for your requirement.
Cheers, Renga
**Award points for helpfull answers**

How to pass payable or ordering vendor addresses using basic type CREMAS01

Hi there!
have a query on how to feed payable and ordering vendor address details to an existing basis type CREMAS01. multiple payable vendors can be existed under one ordering vendor . Currently both OV, PV are being populated at purchase org level and thus both details available under segment E1WYT3M of E1LFM1M. however E1WYT3M doesn't have address related info.
We would like to send all payable vendor address details associate for an ordering vendor via existing CREMAS01 Idoc. Can someone please let me know what are all technical ways to fill address in existing Idoc type? if possible, please share any document to achieve this req. I'm also surfing web at same time.
Thanks in advance.

Thanks for the reply.
The blog talks about specifying the username token policy or specifying the credentials using username and password properties.
What I need to do is pass something like this :
<Authorization>Basic Yw377jbkjbaiudjuo3u=</Authorization>
where,
Yw377jbkjbaiudjuo3u= represents Base64Encoded combination of username and password separated by colon(:) [username:password]
I have set the bpelx:inputHeaderVariable=Authorization under Invoke of MyBPEL.bpel and have used Assign activity to pass Basic Yw377jbkjbaiudjuo3u= as the Authorization value, but it is not working.
In addition, I also tried setting the <property name="oracle.webservices.http.headers">Authorization</property> in composite.xml for the reference service but it doesn't work.
Can you please help me in figuring out what am I missing? Is there any patch that has to be applied for this to work. I am using SOA 11.1.1.5
Please help

Unable to extend the basic type "SALESORDER_CREATEFROMDAT202"

HI
when iam trying to extend the IDOC basic type "SALESORDER_CREATEFROMDAT202" iam getting an error message "Action is not possiable for generated IDOC types"
To my understanding SALESORDER_CREATEFROMDAT202 is a bapi.So, I guess we can not extend these type of IDOC directly.
Can any one can help me how to copy the BAPI interface and extend it....
or any other solution for this......
can any one can help me reg this.....

I will answer my question!
This is the proble of version we are useing!
the extenction is possiable in sap 4.6 version.
but it is not possiable in ecc6.
So follow the steps i have done
created a new basic type "ZSALESORDER_CREATEFROMDAT202"
where icopy the basic type "SALESORDER_CREATEFROMDAT202" to it
Then i extened the IDOC "ZSALESORDER_CREATEFROMDAT202"
and added the new segments.
FInally while assiging the basic type to extended IDOC given basic type as "SALESORDER_CREATEFROMDAT202"
And assigned to the message type "SALESORDER_CREATEFROMDAT2" to it
then we can use this Structure with
Message type: SALESORDER_CREATEFROMDAT2
Basic type: SALESORDER_CREATEFROMDAT202
Extended:SALESORDER_CREATEFROMDAT202EX
for data picking u can code in the followin function modules:
Function Module for Outbound ALE
ALE_SALESORDER_CREATEFROMDAT2
Function Module for Inbound ALE
IDOC_INPUT_SALESORDER_CREATEFR
There is another method also for this:
create a bapi fm with all the requirements and go to swo1 tc create an object with method as BAPI FM created.then go to TC bdbg and create a bapi ale interface.this will automatically generates the inbound and outbound FM's .Then the idoc will be generated with the added segments...

Add IT0006 custom fields for segment definition E1P0006 basic type HRMD_A06

Hello! I am am trying to determine how to bring in our custom fields from IT0006 into our IDOC's for message type HRMD_A basic type HRMD_A06 without performing a custom SAP modification. I was able to create a new segement definition called Z1P0006 and replace the SAP standard E1P0006 IDOC segment defintion in table T777D for infotyp 0006 to Z1P0006. However, I receive a message that I must not maintain this IDOC segment manually and instead you must maintain infotypes and their individual elements by using the transactions for processing infotypes: PPCI or PM01 (Infotype copy transaction for personnel administration).
Does anyone know of a way to bring in the new custom infotype fields from i.e. reimport the table structure for IT0006 into the segment definition without a custom SAP modificaiton? I would really appreciate any help on this topic!
Thanks!
Holly

unfortunately, the standard do not provide the infotypes for the HR-TM (Time Management), that
are between the structures i must send in the other system sap.
Ok, I have never delt with Time data in HRMD_A. Probably this is the case then
Ok,now i've checked the filter in BD64 and the tables BDCP2, CDHDR and CDPOS but it seems
all correct!!
By checking Filters I mean that confirm if you have added Time Infotypes there (just
making sure). If data is appearing in BDCP2 that means there is no problem in Change
pointer creation, Just ruling out possibility.
Try with an user exit it's a good idea, but why in the PFAL the idoc (with the custom segments)
is created without problems and in the BD21 no??? This is very strange
1) Well BD21 uses the Function module (TBDME for HRMD_A) which read change pointers and
create IDOCs. So now if you have extended Segment you have to add your population code
here somewhere.
2) PFAL is Push program, my assimption here is you have wriiten some piece of code to
populate Additinal segments data here? Otherwise IDOC will not be populated
automatically.
Let me know what you think.

IDOC Segement Release vs IDOC Basic Type

Hi there,
we are in an upgrade project and are runing into a general question about idoc creation.
Here is our behavior:
1. We have an reduced IDOC Type in BD53 ZMATMAS based on Messagetype MATMASDI.
2. It has 2 Segements E1MARAM with fields MSGFN MATNR PSTAT and Subsegemnt E1MAKTM with fields MSGFN SPRAS MAKTX.
3. Done the things around (RFC, Partner Profile, distribution model, changepointer ..)
4. In Distribution Model in outbound parameters, added our ZMATMAS.
As parameters we have: Partner type: LS, Message Type: ZMATMAS, Basic Type MATMAS03! and Seg. release in IDOC Type 46B. The Partnersystem is an NoneSAP System.
We are using MATMAS03 because this interface exists since 46B.
Now we send an Material with BD10 and Message Type ZMATMAS.
The Master and Commuidoc are successfull created. In BD87 the commuidoc is an MATMAS03 and has the expected 2 segements E1MARAM and E1MAKTM.
But what we do not expect, if we look into the content of E1MARAM there are ALL Fields which exist for the E1MARAM in release 7.00. Not only our 3 fields MSGFN MATNR PSTAT, or as we second expect only the segemnts that had existed in the segemnt E1MARAM in release 46B of MATMAS03.
The additional fields were filled with the NODATA sign.
My question is: Is it correct that an IDOC with basic type MATMAS03 can have an segement E1MARAM which is formated like the segemntdefinition E2MARAM007 (Release 7.00 / 6.03)?
The difference is definatly the length of the field! 876 in 7.0 vs 757 in 4.6A.
Why is SAP using the highest available segemnt release regardles which basic type we choose?
Isnt this wrong?
Additional infos:
We know that it is not possible to have an IDOC with basic type MATMAS03 with an segement e.g. E1MARA1 which only exists in newer basic type MATMADI if segemnt release is set to 46B in our distribution model.
Failure is: Segment E1MARA1 is unknown in Release 46B/ (correct and expected behavior)
If we are using this scenario with not an reduced message type, we will only find the fields in E1MARAM which are filled with data. (Not all fields of the latest release with nodata)
I traced the MASTER_IDOC_CREATE_MATMAS and hit the function IDOC_REDUCTION_FIELD_REDUCE. As you can see in it, it first checks if the idoc is an reduced message type, and at the end, fills up all fields with the "empty_symbol" which have no data in it. Why is this only happening if it is an reduced message type?
Kind regards
Manuel

Additional Info:
In WE21 at the TRFC Port, it is possible to set this Option:
Send Only Fields of Selected Segment Version
The segment data of the IDoc is passed to this port with the length matching the segment definition of the release specified in the partner profile.
But if we are using an reduced message type, all fields of the newest release are in the segement.
The docu tells that this will be done in function EDI_DOCUMENT_OPEN_FOR_CREATE.
But it is never called when createing an material IDOC with BD10.
Bug or feature?
Kind regards
Manuel

What is Basic type in IDoc?

Hi all,
What is Basic type in IDoc? Please explain me in layman terms. How to see the details of basic type ALEREQ01? Please point me to related files or threads.
Thanks,
Charles.

Hi,
IDOC Basic type means, IDOC type delivered by SAP. When you want to modify the IDOC provided by SAP, you create an Extension IDOC of Basic type.
This is what SAP says about "Basic Type".
IDoc type supplied by SAP (standard format for data communication). Basic types can be modified by customers to create a new, upward-compatible IDoc type. Basic types can also be defined by customers and modified at a later date. Basic types and subsequent modifications created by customers are not necessarily upward-compatible.
To check detail of any IDOC, user transaction WE60.
Check area Menu WEDI. Its a Area menu for all IDOC related transaction. Enter command WEDI ( where you enter transaction code - Top left of screen ). Also, this command only works from very first screen of SAP. This is SAP eacy access screen you see when you logon into SAP. Since WEDI is area menu, you can only execute from very first screen.
Here is the list of other area menu.
WEDI - IDOC and EDI Basis
BALE - ALE Administration
Let me know if you need any other information.
Regards,
RS

Diff between Idoc type and message type

Hi Friends,
I have a created a message type and IDoc type with similar name ZVOU_IN_LYNX .
If I have the similar names for these two , is there any further future related issues.
kindlly suggest on this issue ASAP.
Regards
Punjaala

Hi ,
idoc type is a comibination of Segments it is like a structure.
Message type actually tells the meaning of idoc..
Message type + iodc type + exension idoc type used in furthe uses..
here actually idoc type come to use..
we30 Idoc type          "single Idoc type--with basic type..
we30 idoc type         "multiple idoc with above copy called extension idoc..
WE81 Message types: Create a new messagetype         "Single message type
WE82 Idoc Type/Message: Create Entry to link the above defined message type with the IDOC + "extension....
WE57 Message/Application object: Create entry for Functionmodule/IDOC type/Messagetype/Object
Edited by: Prabhu Das on Apr 17, 2009 7:27 PM

Idoc type and message type for request for quotation

hi

MM Side...
Message Type REQOTE
Basic type ORDERS05
SD side..
Message type QUOTES
Basic type ORDERS05
Process code SD12
"Reward point if usefull"
Thanks,
Narayan

What are the message types available for Vendor Address?

Hi Everybody,
I need to read the all the change pointers of Vendor Address using the function moudle 'CHANGE_POINTERS_READ'. To call this FM I need to pass Address's Message Type. I am passing ADRMAS as message type. but i am not getting any records into change pointers internal table.
Pls help me out by informing the message type of Vendor Address.
Regards,
Nagaraju Maddi

Hi,
The address group is in the segment E1BPAD1VL1-ADDR_GROUP.
Check the table TSAD7 for Address groups (central address management)
Reward points
Regards

IDOC approach (Basic type : CREMAS01) to upload legacy vendors

I am using the IDOC approach (Basic type : CREMAS01) to upload legacy vendors.The LSMW then creates default partner functions.
However i need to modify the partner function.
My question is ...Is there a way to delete an entry through LSMW using IDOC approach (or even modify would help) but not append????
Thanks in advance ,
naval kishore bhatt.

Hi,
Anybody please tell me the reason for the following error, despite giving all the field values mentioned there. The same error occurs even if I run the BAPI (which the ARTMAS iDoc uses) directly by passing values.
The field MARA-MEINS/BAPIE1MARART-BASE_UOM(_ISO) is defined as a required field; it does not contain an entry
The field MARA-TAKLV/BAPIE1MARART-TAX_CLASS is defined as a required field; it does not contain an entry
The field MARA-TRAGR/BAPIE1MARART-TRANS_GRP is defined as a required field; it does not contain an entry
The field MAW1-WLADG/BAPIE1MAW1RT-LOADINGGRP is defined as a required field; it does not contain an entry
Regards,
Gowri.S

Vendor Address in IMessage type ORDERS basic type ORDERS01

Similar Messages

Maybe you are looking for