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

Similar Messages

IDoc : Linking Basic type and function module

Hi,
I am in the process of customizing for inbound processing.
I have one doubt reqarding below customizing :
t-code WE57:
FM                               Message type          Basic type
ZBAPI_IDOC                ACC_DOCUMENT   ACC_DOCUMENT01
ZBAPI_IDOC                ACC_DOCUMENT   ACC_DOCUMENT02
t-code WE42:
Process code     FM                                   Message type
ZBAPI                ZBAPI_IDOC                    ACC_DOCUMENT
So in this scenario, which Basic type would be considered? or if I want the Idoc with basic type ACC_DOCUMENT02, then how should be the customizing?
Thanks ,
Yogita

Hi Yogita,
The basic type depends on the version of system in consideration.
lets say for eg. HRMD_ABA has basic type from HRMD_ABA01 to 05 and they are depend on the version of the system as which to use.
Regards,
Atish

Idoc of basic type INVOIC01 freight charge feild

Could any one tell me how to Identify a field on the Idoc of basic type INVOIC01 to populate the freight charges in SAP.
Need to find whether field is available or not. This is for inbound idoc. Pls give the inputs
Thanks in advance

Hi,
You can see the IDOC documentation alongwith fields using transaction WE63.
I dont think, the field you are intereseted in is in INVOIC01.
I have checked. You also check once.
Regards
Abhii

Error in idoc of basic type artmas05 - status 51 with Message no. MG537

Hi all,
I tried to upload the material master table through idoc creation of basic type artmas05. But when i'm trying to do that i'm getting status 51 with Message no. MG537. then I analysed the application log which displays the following
*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
*You have not fully maintained the tax classifications
*The field MAW1-WLADG/BAPIE1MAW1RT-LOADINGGRP is defined as a required field; it does not contain an entry
But i hv given values for all the above fields in their respective segments.So can any1 suggest me how to proceed further.
It would be helpful if someone could tel me the required fields in idoc to upload material master table through idoc.
Thanks in advance,
Revathi.

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

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

IDOC and Basic Type

Hi Experts,
I have a basic type that I will use in my IDOC with no process codes(attached FM) that will create a document (e.g. orders, deliveries)... and I have found out a BAPI that I can use in creating the document.. the question is.. do I still need to CALL FUNCTION 'IDOC_WRITE_AND_START_INBOUND' after calling the BAPI to create the document?
Thanks!
Nosaj

Hi,
Thanks. To clarify.. first I will receive an IDOC coming from XI this IDOC containes the planned orderse that I will create in SAP.
Question: Can one IDOC contains a lot of planned orders to be created? Meaning that I have created a copy of segment E1PLAFL because this segment can only acquire a maximum of 1 data record... so i copy it and customize it to acquire more than 1 data records.....?
Then the Basic Type: LOIPLO01 does not have a functionaly of creating planned orders.. so I will use a BAPI in creating the planned orders....
Question: Since I will be using a BAPI to create the IDOC.. do I still need to call the function module ive said (WRITEIDOC)?

IDOC with basic type INVOIC01 help !!!

Hi experts,
In this idoc type INVOICE01, where I can see the customer number?
I created a function module to process this inbound IDOC and trying to get sales orders by BAPI function module BAPI _ SALES_GETLIST , but I don't know how to get the customer number to fill in this function module.
Thanks,
Gy

Hi,
I viewed the structure E1EDKA1.
I found out the value of this segment in my inbound IDOC. Its partner function code: RE, LF, PI.
Could you explain that, and tell me which the partner function can I get the value of field vendor number (LIFNR - Vendor number at customer location ) and assign to customer number?
Thanks,
Gy

Trigger WBS idoc with basic type PROJECT01 when ever saved

Hi
I have requirement where idoc has to trigger each time the field value is changing to replicate changes to master data through a new document. And also only WBS elements with Project Type = 'TS' (Time tracking level). I am new to Idocs. Please hlp me how to do this. I have to use PROJECT01 idoc type.
Regards,
Lohitha

Hi,
Please refer to the below thread. Hope it helps.
Triggering workflow upon idoc fail
Regards,
Sridhar

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

IDoc basic type FIDCCH01 with error F5866

Iu2019m trying to create an iDoc with basic type FIDCCH01 and message type FIDCCH type. Iu2019m getting error F5866 u201CWhen calling up the interface to financial accounting, no entry was made in the transfer parameter "Application key" when I process the idoc. I do not see an idoc value by this name. What am I missing in my config?
Thanks,
Stan

Stan,
First, I'd like to mention that you determine where the error message F5866 is used by entering this message in transaction SE91 and pressing the where-used function. This won't show you any of the dynamic message calls, but it does indicate that function modules FI_DOCUMENT_CHANGE and FI_DOCUMENT_CHECK_CHANGE are both possible origins for the message you received. These function modules are part of the FI Interface which I am assuming is called during the processing of your IDoc.
ACCHD-AWREF is one of the values passed to the FI Interface function modules, and message F5866 is returned when that field is blank. This is why I assume that the IDoc in question is missing a value for the AWREF field.
Based on that assumption, I checked the definition for the IDoc type that you mentioned, FIDCCH01, via area menu WEDI. This IDoc type contains a segment E1FIREF with field AWREF. You can use transaction WE02 to display the IDoc causing the error and check to see if the actual data for E1FIREF-AWREF is blank (ultimately leading to the blank ACCHD-AWREF value and error F5866).
Cheers,
Jamie

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

Creation of IDOC with message type INVOIC01

Hi All,
I am trying to create a new IDOC with message type INVOIC01.
When I see transaction WE81, I observe that the required message type INVOIC is available. Also in WE82 the basic types INVOIC01, INVOIC02 and INV_ID01 are attached to the message type INVOIC.
However, while trying to create an IDOC in WE19 using a message type, I get options to create against INVOIC02 or INV_ID01. The basic type INVOIC01 is not getting populated because of which all the IDOC that I create are of basic type INVOIC02.
The client wants me to create IDOCs with basic type INVOIC01.
Can anyone please help?
Thanks in advance.
regards
Nagarajan

Hi Nagaraj!
I've looked at the documentation and did not find information, which would help me. Should I use in my case z-segment to put extra lines or there is some qualifier in segment E1EDP02 (Document Item Reference Data), which triggers to another referencing (not PO or delivery note)?
Thank You,
Natalija

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...

Problem in generating an IDOC from Output type

Hi Experts,
I am trying to generate an IDOC of basic type "OILSHI01" using the custom output type. in my scenario the output type gets issued , but IDOC does not get generated , i have checked the configuration in NACE transaction .
Can you please help me understand what can be other reason why this IDOC does not get generated?
Regards,
AshiSh Shah

Hello,
Did you try to debug the idoc generation program & where it fails to put together the internal data into IDoc?
That should help you identify problem.
If configuration settings is correct ,port settings are correct & partner profiles are correctly mapped for necessary Idoc creation,it should work.
Hope this helps.
Thanks.

How to change the default IDOC basic type from CREMAS05 to CREMAS04.

Hi All,
How to change the default IDOC basic type from CREMAS05 to CREMAS04 when sending Vendor Master Data.
When I generate partner profile, the system will add the latest version of IDOC type which is CREMAS05 to the Outbound message. In my project, I'm asked to use CREMAS04.
I want to use BD14 to send master data directly, but the program will generate IDOC using CREMAS05. Is there a way that I can change it to CREMAS04? And also for using Change Pointers, I want to use the report RBDMIDOC, but i have the same problem.
Thanks
Sai Krishna

execute WE20 and edit the outbound parameters
here is a pretty good example: http://documentation.softwareag.com/webmethods/sapr3_gateway/sap231/pages/sapdist.htm
Edited by: Jürgen L. on Sep 7, 2011 9:49 PM

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

Similar Messages

Maybe you are looking for