Vendor idoc

I am using CREMS04 to try and create a vendor master record. However I am getting an erro saying invlaid function code. I am using the message code 009 to try and create the IDOC. Can anyone shed some light on how to create a simple vendor master record via an idoc.

I've taken out the 009 codes but still getting the same error. Any ideas?
I've ran the test idoc in the foreground and the underlying BDC performed by the Function Module gets stuck at the Purchasing data screen as its trying to enter the BDC code '=LTSU'. I'm not even putting any data in this screen but I have tried to add default data wiht no joy...
Message was edited by:
showthousand

Similar Messages

How to send vendor IDOC data from SAP R/3 to XI.

Hi experts,
I have developed the IDOC to FILE scenario for Vendor Master Upload. I want to place flat file in local folder with in XI or Outside of XI. (Using NFS or FTP protocol in FILE adapter). My First quesstion is How to setup Folder with in XI ro Out side XI?
And also I want to push the IDOC from SAP r/3 to test the scenario. Both XI and R/3 systems are configured to exchange data.
How to Push Vendor IDOC from SAP R/3 to XI? (we can send XML directly to XI; but the R/3 kernal should be moe than 6.20).
Thanks in Advance.....

Hi,
>>My First quesstion is How to setup Folder with in XI ro Out side XI?
Its a normal way to creation of folders in Os level . u can create the folder in XI Server or on the FTP Server.
ALE Settings
Steps
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.
IDoc-XI-File scenario
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
Posting the IDOC from R/3 to XI
/people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi
REgards
Seshagiri

Standard Vendor IDoc CREMDM04 needs to be triggered from the transactions

The Standard Vendor IDoc CREMDM04 needs to be triggered from the following transactions:
u2022XK01 (Create Vendor)
u2022XK02 (Modify Vendor)
u2022User Exit EXIT_SAPOTM_VEND01 .
The following are some more details:
u2022Receiving System: SAP PI
u2022Sending System: SAP ECC
u2022Direction: Outbound from SAP ECC.
How do we achieve it ??
BR.
Tan
Moderator message: please do more research before asking, show what you have done when posting.
Edited by: Thomas Zloch on Feb 20, 2012

Hi,
In Tx. WE42, Select the process code for the corresponding partner and bind your workflow / task inplace of the function module with the process code. Now, this will enable the idoc to get placed in the agents(identified by that workflow)inbox.
But to design the workflow, you`ll have to use tx. swdd and prior to that get some basic understanding of Business Workflow from SAP Library.
Hope the info. is helpful and reward points if so.
Regards

Vendor IDOC failures

Hi Experts,
We have series of Vendors Masters updated through CREMAS IDOCs. But some of the CREMAS IDOCs fail as the BANK key in the Vendor is blocked by another user.
Actually the Mass vendor update happens as a result some of the bank keys will be locked up and a result IDOCs fail.
Can we have a solution for this scenario?
1. Vendor IDOC is updating a vendor master with a same bank key
2. another IDOC is updating another vendor master with a same bank key.
The second IDOC fails, can we avoid this ?
Please give a solution for the same.
Thanks,
Rohan

Hi,
I can suggest one solution, You can find a user-exit in inbound FM( you can find this FM in inbound process code).
Write a code in user-exit to check if the bank key is locked by other user by applying a lock and if it fails that's mean it is locked by other, put a wait time and try again.
Thanks,
Sajid

Vendor IDOCs are not uploading in LFA1 table

Hi All,
We have a SAP system where Vendor IDOCS are coming from MDM through SAP PI middleware. The problem we are facing is we are not able to see all Vendors in LFA1 table.
In WE05 IDOCS are posting successfully but when we check for respective vendors in LFA1 table only few vendors are available there.
Can anybody guide us to solve this issue? Also pls let us know the process of uploading master data into table as we are very new in ABAP.
Regards,
Sarita

be open minded. SAP gives several import methods to load vendors. one of them is per IDOC.
But the vendor master IDOC does not automatically create the adress master.
And even more important, if you migrate data from one SAP system to another, the IDOC method is more straight forward than the batch input, because you can send the IDOCs from legacy system to new system, you will then have a 1:1 relation of the structure in LSMW and you can create vendor masters by knowing the new vendor number from an internal number range already in LSMW, long before you actually post the vendor. With batch input you can either post with numbers from external number range, or you just dont know the new number already in LSMW.
And you dont need to download the data to Excel. And further, the LFA1 adress data has less information than the ADRC adress data.

CREMAS05 Vendor idoc other fields

Hi,
Basic type CREMAS05
Vendor master data distribution
Released since Release 700
1). In idoc it is showing the
REGIO : Region (State, Province, County)
& LAND1 : Country of company only, but i want its text.
Ex: For 22 - Tamilnadu &
for IN - India.
2). When i set a Deletion flag for any vendor using T.Code XK06, in generated idoc,
LOEVM field value will be 'X',
if vendor is active its value is ' '.
LFA1-LOEVM-Central Deletion Flag for Master Record
E1LFA1M : Segment for general vendor data
LOEVM : Central Deletion Flag for Master Record
i hv to put the constant value TRUE, if vendor is active &
FALSE if deleted, for the mapped field in XI.
Pls let me know hw to solve the above requirement.
Regards,
Balaji

Hi,
IDoc contains 2 Segments:
Seg1 & Seg2.
Seg2 is the child of Seg1.
Seg1 contains field:
CODE
Seg2 contains fields:
DESCRIPTION
HIERARCHY
When i trigger the idoc, the data is stored as:
Seg1:CODE: 1001
Seg2:DESCRIPTION: test1,
HIERARCHY: 00
Seg1:CODE: 1002
Seg2:DESCRIPTION: test2,
HIERARCHY: 01
Seg1:CODE: 1003
Seg2:DESCRIPTION: test3,
HIERARCHY: 02
Seg1:CODE: 1004
Seg2:DESCRIPTION: test4,
HIERARCHY: 03
creating the duplicate segments as shown above.
This data is mapped to the structure in XI.
The structure to map will be as follows:
str1
---ID1
---DES1
---ID2
---DES2
---ID3
---DES3
i've to map depending on the field HIERARCHY condition.
IF HIERARCHY = '02' THEN
ID1 = 1003.
DES1 = TEST3.
IF HIERARCHY = '01' THEN
ID2 = 1002.
DES2 = TEST2.
IF HIERARCHY = '00' THEN
ID3 = 1001.
DES3 = TEST1.
How to map this condition based, in the MESSAGE MAPPING?
pls help in solving this if possible with a screen shot.
Regards,
Balaji

ALE IDoc : Vendor Master : Cremas: Inbound IDocs are bypassing the Customiz

Hi,
Create Vendor master inbound IDocs - CREMAS - are overridding the customizing settings.
For example for a particular vendor group a number range is set in customizing.
When we try to create a vendor through XK01 which does not fall in a particular number range as set in customising for a particular vendor group, we get a error message and creation is terminated.
But if the same vendor is created via standard idoc CREMAS, vendor is created without any errors bypassing the customizing settings.
So can anybody help me in this. Is there any customising setting that we need to do explicitly for Vendor IDocs. Or any other setting in standard IDoc.
Thanks in advance.

Hi,
1. If your vendor changes should be updated from one system to other system through ALE, we need to active the change pointers.
2. Change points can be activate through Tcode SALE
3. After activating change points and your distribution model is ready, you can execute the program RBDMIDOC to genarate the IDOCs.
4. Normally this program will be executed in the background
5. And as you said, you have to do some validations before sending IDOCs. For this you can Filters and rules in the DM.
OR you can write the code in user-exists of outbound posting program.
Rewards if this info is useful.
Thanks,

EDI Vendor posting (INVOIC01) to account assign Profitability segment

Hello Experts,
Have anyone used INVOIC01 (EDI vendor) Idoc type to post to a Profitability segment in a InterCompany sales scenario? If yes, could someone guide me how to achieve this? I see that OBCC transaction has Profitability segment field, but I am not sure how to use it.
Any ideas?
Thanks for your time.

Thanks Waman for the SAP notes.
In fact, I have looked at those notes, already. We cannot change to INVOIC02 Idoc type.
I wonder, why SAP does not offer the functionality to update Profitability segment on the EDI Vendor posting. Transaction OBCC has Profitability segment, but giving a fixed PSEG will not meet any business requirement! EDI enhancement FEDI0001 has only EDI-FIELDS and not the IDoc segment details. There is nothing much one can do with just the EDI-FIELDS.
Have you used FEDI0001 enhancement for PSEG determination? Looks like all that one can do with FEDI0001 is move the OBCC configuration values to Coding block.
Thanks for your time.

Reg: Vendor E-mail address transfer in ALE

Hi Gurus,
We are currently in a process to transfer vendor master and customer master to GTS system(SAP system)
so i have implemented change pointers for this. in BD53 i have done reduction as well .
i don't want the e-mail field to be sent to GTS system. but it is still moving to GTS system.
can anybody advice me , how to prevent this?
Thanks in advance
S.Janagar

Adresses and emails are stored in central address managment tables.
The part of address that you see in vendor IDOC is just the part that can be seen in LFA1 table.
To transport the address from central address managment you have to use IDOC ADRMAS
see OSS note 384462 - Master data and addresses
for full detail and recommendations

IDOC type for customer master

Hi friends,
Could anyone explain me about...
<b>
Use existing IDOC types to send the customer master data, vendor master data and material master data from the sender system to the receiver system.</b>

Hi,
Please maintain distribution model (BD64) and partner profile (WE20), RFC connection (SM59) for message type DEBMAS (customer), DEBMAS (vendor) and MATMAS (material master).
Once the above configuration done, then you can use the following transactions to send the IDocs.
1. BD12 - Send Customer IDocs (Sender -> Receiver) or
     BD13 - Get Customer IDocs (Receiver -> Sender)
2. BD14 - Send Vendor IDocs (Sender -> Receiver) or
     BD15 - Get Vendor IDocs (Receiver -> Sender)
3. BD10 - Send Material IDocs (Sender -> Receiver) or
     BD11 - Get Material IDocs (Receiver -> Sender)
Regards,
Ferry Lianto

Combine into one IDOC

Dear FI Idoc Gurus,
Iu2019m using basic type PEXR2002 , this idoc is generated when I do a payment run via F110. The idoc generation as far as I know is standard , with some enhancement done via user exit - EXIT_SAPLIEDP_902.
Currently for each payment document generated one IDOC is created . The Business document / payment document is per vendor. Hence each vendor I get one IDOC .
Client is asking if I can combine payments of various vendors into one IDOC ? is this possible? Is it possible through heavy customization?
Please assist thank you.
Best Wishes

Hi,
I guess its very difficult to combine the different vendor IDOC into single IDOC and require the customized development.
Instead you can collect the different vendor IDOC based on the specific parameter. so that all the IDOC will get collected and send as a single message or single file. for this you can use the IDOC collect functionality.

Idoc Type for Vehicle Master

Hi Friends,
Can any body tell me the Idoc type for
1. Vehicle Master 2. Transport unit and their respective transaction code to send data.
Points would be awarded for useful answers.
With Regards
Vasu

Hi,
Please maintain distribution model (BD64) and partner profile (WE20), RFC connection (SM59) for message type DEBMAS (customer), DEBMAS (vendor) and MATMAS (material master).
Once the above configuration done, then you can use the following transactions to send the IDocs.
1. BD12 - Send Customer IDocs (Sender -> Receiver) or
     BD13 - Get Customer IDocs (Receiver -> Sender)
2. BD14 - Send Vendor IDocs (Sender -> Receiver) or
     BD15 - Get Vendor IDocs (Receiver -> Sender)
3. BD10 - Send Material IDocs (Sender -> Receiver) or
     BD11 - Get Material IDocs (Receiver -> Sender)
Regards,
Ferry Lianto

Steps to create outbound CREMAS IDOC from ERP

Hi,
Can you please share the steps to create outbound IDOC from ERP system?
Business requirement is that whenever a new vendor is created in the ECC system, SAP should trigger an outbound vendor IDOC CREMAS from ERP system. Also whenever the vendor data is changed then the entire vendor details should be passed to outbound IDOC and not just the delta changes. Change pointer can be configured but to create idoc for full vendor records.
I guess we can use CREMAS.
Can anyone please share the steps to configure it in ERP?
Regards,
Sandeep

1. Read the file using OPEN DATASET and read and fill up the segment info and fill the EDIDC header data
and then call function
CALL FUNCTION 'INBOUND_IDOC_PROCESS'
    TABLES
      IDOC_CONTROL       = i_edidc
      IDOC_DATA          = i_edid4.
a®

Idoc Error - EDI: Syntax error in IDoc (segment cannot be identified)

Hi All,
have created a new reduced message type for our new vendor A/C group through BD53. Also done reqd config for sending the vendor master through this message type. .
I have created couple of vendors for testing with X01 with withholding tax functionality and when try to send these vendors , Idocs are getting failed .
When I create vendor without withholding tax functionality , idoc is getting posted succesfully . If create vendor with entries in the feild whih are related to withholding tax . Idocs are getting failed .
If I see the status in WE05 ,Idocs which are posted succefully are showing the basic type as CREMAS03 . For idocs which are getting failed have the basic type as CREMAS04 and also the extension as Z1CREMAS . I don`t understand why the system is defaulting CREMA04 & Z1CREMAS when I send the vendor master with withholding tax feild entries.
I am not much familiar with ALE /Idoc set up. Please can any body help me to resolve the issue.
The error message in we05 as below
EDI: Syntax error in IDoc (segment cannot be identified)
Message no. E0078
Diagnosis
The segment Z1LFA1M does not occur at the current level of the basic type CREMAS04 (extension Z1CREMAS).
This error can have several reasons:
The segment Z1LFA1M is assigned to a group whose header segment does not occur.
The segment Z1LFA1M does not exist in the syntax description of the basic type CREMAS04 (extension Z1CREMAS).
The sequence of segments in the group in which the segment appears is incorrect.
Previous errors ('mandatory' segment or group missing) may be due to this error.
Procedure
Please check the IDoc or the syntax description of the basic type CREMAS04 (extension Z1CREMAS).
Thanks

Hi,
I don`t understand what do you mean release after adding segment.
Message type works i.e. Idoc get posted if I send with the vendor w/o withholding tax field entries. Idoc fails when send vendor with withholding tax field entry.
Regards

Transaction to see result of inbound idoc ( XI to SAP R3) ?

Hi,
may i know the transaction to see whether the inbound idoc has created the record ?
i'm sending idoc from XI to ECC.
Farah

Hello Farah ,
You can check the inbound idoc status in R3 using WE02/We05. In case want to do a search on idoc based on the timings , message type , target system etc use WE09 . Do remember to mention the search field like MATNR for material idoc , KUNNR for customer idoc or LFA1 for vendor idoc etc.
Idoc in status 53 means success and staus 51 failure.
Hope that helps!
Cheers
Binoy
Edited by: Binoy Thomas on Apr 24, 2008 7:33 PM
Edited by: Binoy Thomas on Apr 24, 2008 7:34 PM

Vendor idoc

Similar Messages

Maybe you are looking for