Cremas03 data??

Hi Guys,
This is my first question in this forum.
I am implementing a scenario where in i am passing data from FTP server to R/3 (IDOC) through XI
The idoc is CREMAS03.
Now the scenario is working fine but when i use we05 to check if the IDOC was posted or not i get the error message:
<b>CODE 51: Field ADDR1_DATA-NAME4 . does not exist in the screen SAPMF02K 0111</b>
Could someone tell me what is that i am missing???
The data I am passing to IDOC is:
- <CREMAS03>
- <IDOC BEGIN="1">
- <E1LFA1M SEGMENT="1">
<MSGFN>009</MSGFN>
<LIFNR>320123</LIFNR>
<ANRED>COMPANY</ANRED>
<KTOKK>LIEF</KTOKK>
<LAND1>US</LAND1>
<NAME1>Rodrize</NAME1>
<NAME2>Constant</NAME2>
<ORT01>Melbourne</ORT01>
<PSTLZ>3204</PSTLZ>
<SORTL>enjoy</SORTL>
<STRAS>Anothony St</STRAS>
- <E1LFB1M SEGMENT="1">
<MSGFN>009</MSGFN>
<LIFNR>320123</LIFNR>
<BUKRS>3000</BUKRS>
<AKONT>31000</AKONT>
<FDGRV>A1</FDGRV>
</E1LFB1M>
- <E1LFM1M SEGMENT="1">
<MSGFN>009</MSGFN>
<LIFNR>320123</LIFNR>
<EKORG>3000</EKORG>
<WAERS>USD</WAERS>
</E1LFM1M>
</E1LFA1M>
</IDOC>
</CREMAS03>
pls advice...
Regards,
Ashish

The screen field in your error is not on the batch job please use the filed
ADDR1_DATA-STR_SUPPL3 in your idoc instead of Field ADDR1_DATA-NAME4
check it out

Similar Messages

CREMAS03 - Company Data Creation

Hi All,
I am trying to send vendor data in to R/3 4.6c using CREMAS03. When is send company information, i get the following error: "No company codes have been allocated to cross-system company code XXX". I am looking for a transaction which will help me to do assign company code for cross system company code. But i Could not find any. have anybody come accross this situation?. Do anybody know the transaction?. your help will be much appreciated.
Regards,
Arul

check /change setting in OB72 or OBB5.
more info In SALE settings.Search terms are CROSS SYSTEM
Regards
Prabhu

SEGMENT FOR WITHOLDING TAX DATA FOR IDOC CREMAS03

Hi all!
Is there any segment for withholding tax data when creating creditor master data with IDoc CREMAS03? I need an other IDoc for this purpose?
Thanks in advance
Zapla

Dear Atul,
In function module AC_DOCUMENT_CREATE there is the structure
T_ACCWT to pass the calculated tax items. In the
BAPI_ACC_DOCUMENT_POST the corresponding BAPI structure has been added
with release 6.0. For older releases it is posssible to pass the
withholding tax items in structure EXTENSION1 and map it to T_ACCWT
using a customer exit or the Business Transaction Event RWBAPI01.
For the corresponding IDOC ACC_DOCUMENT the same holds.
From release 6.0 on there is the IDOC segment E1BPACWT09 for
passing WT information, in older releases E1BPPAREX
can be used to pass the extension data, see note 487722.
I hope this can help You.
Mauri

Fields missing from CREMAS03

I am tasked to update vendor master data using IDOCS and i immediately thought that CREMAS03 will do the job. However i am having difficulty in finding the following fields in the idoc
1. SMTP_ADDR - mail address
2.DEFLT_COMM - Standard Comm. type
3. Building Code, Room and Floor
4. House No
5. Telephone extensions
Are they really missing from the IDOC?. is there any other mechanism to populate these fields?. You help will be much appreciated.
Arul

More info:
I looked at the IDOC structure using we60 before posting here. I can not find these filds. is there any trick in passing these fields? is there any other alternative method of updating these fields?.

Error while posting the CREMAS03 Idoc

Hi
I a getting the Error while posting CREMAS03 idoc from File
The ERROR: Status 65 ,Error in ALE Servics: Cross Company code does not exits..
but when i cheked with the functional guys , the comany code exits..
Any one have any idea
SV

Hey,
    seems you have given wrong enteries for logical system in sale or in WE20(patrner profile)
Steps for ALE settings:-
Steps for XI
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the R3 system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto IDX1.
     Create a new port.
     Give the port name.
     Give the client number for the R3 system.
     Select the created Rfc Destination.
Step 3)
     Goto IDX2
     Create a new Meta data.
     Give the Idoc type.
     Select the created port.
Steps for R3.
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the XI system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto WE21.
     Create a port under transactional RFC.(R3->XI)
     Designate the RFC destination created in prev step.
Step 3)
     Goto SALE.
     Basic settings->Logical Systems->Define logical system.
     Create two logical systems(one for XI and the other for R3)
     Basic settings->Logical Systems->Assign logical system.
     Assign the R3 logical system to respective client.
Step 4)
     Goto WE20.
     Partner type LS.
     Create two partner profile(one for XI the other for R3).
     Give the outbound or inbound message type based on the direction.
Step 5)
     Goto WE19
     Give the basic type and execute.
     fill in the required fields.
     Goto IDOC->edit control records.
     Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
     Click outbound processing.
Step 6)
     Go to SM58
     if there are any messages then there is some error in execution.
     Goto WE02.
     Check the status of the IDOC.
     Goto WE47.
     TO decode the status code.
Step 7)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.

Updating Standard comm type in vendor master idoc- CREMAS03

Hi all,
We have requirement of processing inbound vendor master data.We are using CREAMS03 idoc type as our system is 4.6C.
While updating venor master in general data we are not able to update the field Standard communication type.
Can anybody help me to find out which is the field needs to be filled to update the standard comm type in vendor master?
if this field is not present in CREMAS03 then do we need to customise our idoc???
if partner system sends this field in some other balnk field then how to map this field in BDC??? is there any enhancement?
I am using process code CRE1 which is calling IDOC_INPUT_CREDITOR function module.
Please suggest.
Thanks in Advance,
Raghavendra

I buy your point.
I will create WHT Type for WHT Code - Individual and WHT Code - Others.
But still there will be an issue since WHT Code will be different Non PAN and With PAN (within Individual). So still this will be an issue.
How to control this now.
=
Meena

Creating / updating vendor master from CREMAS03

Hi All,
I am getting vendor master data from external system and SAP XI will convert this into Idoc of message type CREMAS03. I would like to create/update vendor master in R/3 system from Idoc CREMAS03. Which function module / BAPI will cater to this need.
Thanks and best regards
Kalingeri

Hi
Check in WE57 using the Message type & Idoc type & direction.
IDOC_INPUT_CREDITOR & IDOC_INPUT_CREDITOR_MDM are the the two Func modules being used. You can use any one of them based on your reuirement
Thanks & Regards
Kishore

IDOC ADAPTER Issue, some meta data loads, some doesn't

Hey all,
I just started trying to setup the IDOC adapter connection between our R/3 system and our XI system. I decided to try and pull in some meta data via IDX2 to start. The weird thing is that I get some IDOC structures successfully, but not others. I think it has to do with some requirnments that I am missing on the R/3 side. For instance, outside of setting up the RFC connection, creating the tRFC port and the partner profile for the Logical system what else is needed. Do I have to assign the basic type to the outbound partner profile to access it? Do I have to actually create IDOCS for the basic type? Just curious. Here are the details of what I have done so far. A lot of this I pulled from other peoples postings here on the forum, I think I am just missing a few steps!
Our current configuration is as follows:
SAP R/3 Enterprise to post IDOCs to XI .
- R/3 Configuration:
logical system created: DXICLNT200
we20 : Partner Type LS: partner number: DXICLNT200.
we21 : IDOC Ports: Transactional RFC: Port name: DXICLNT200. IDOC record type SAP Release 4.x. RFC Destination : DXICLNT200
sm59 : create RFC destination : DXICLNT200. Target host: the XI box. Logon security: Client 200. XIAPPLUSER. PASSWORD (for XIAPPLUSER). Testing the connection works.
- XIHOST Configuration:
sm59 : created RFC destination to DDSCLNT210. Gateway options used, NO Client or User specified, are these needed, if so, is there a particular user to use.
Test connection works.
IDX1 : Created Port - DDSCLNT210. client 210. RFC destination DDSCLNT210.
IDX2 : Able to load metadata for IDoc Type CHRMAS01, of port DDSCLNT210. NOT ABLE TO IMPORT CREMAS03 or MATMAS03!
Any help is greatly apprciated!
Thanks,
Chris

There was a problem in the RFC connection, the target host was not populated correctly. All meta data can now be pulled.
However, I am curious about where the meta data for CHRMAS and CLSMAS came from. the RFC connection was NOT working, so where could it have pulled this information from????

Basic type CREMAS03 does not exist

Hi all.
We have SRM 7 Classic Scenario with ECC 6.4
My problem is in scenario MM-SUS. When we try to replicate a vendor data from MM to SUS the idoc MM is processed correctly, but in (SUS) has an error in trx WE05: Basic type CREMAS03 does not exist.
I review the settings and I can not find the cause.
any idea about that?
Regards

Hi,
I am not clear with your issue. Why are you checking for idoc status in SUS system?
IDOC is sent from the ERP system and check what the status of IDOC is in ERP. Next check whats the xml status in PI system and if its successful in PI then check xml in SUS system/. You can check xml status using tcode: sxi_monitor.
Regards
Sam

Data migration from ECC5.0 to ECC6.0

Hi All,
Is there a standard SAP utility to migrate the data from ECC5.0 to ECC6.0? Assumption is that all the standard fields and the transactions are same. Good example for this case is standard material master, Purchase order, purchase info record etc.
Currently I am planning to extract the data from source system (using custom program or table download etc...) and upload the data into target system (using LSMW, eCATT, BDC etc...).
Is there a standard way to load the data into target system without extraction and upload? Please let me know.
Thanks
Nagarajan

ALE Customizing
1)     IMG > Application Link Enabling (ALE) > Sending and Receiving > logical systems > Define Logical System: name it XXXXXX
2)     IMG > Application Link Enabling (ALE) > Sending and Receiving > Systems in Network > Asynchronous Processing > Assigning Ports > Define Port: name it XXXXXX   Description: Files for Migration to YYY
The port need to be defined beneath FILE
The IDOC record types for SAP Release 4.x need to be selected
A physical directory is needed. One must be able to map this directory with the Windows explorer to copy the file to the network or local drive.
Function module: EDI_PATH_CREATE_CLIENT_DOCNUM
In order to prevent unprocessed files being overwritten, you use function modules which generate file or directory names dynamically, that is to say, at runtime.
3)     IMG > Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Cross-Application Settings > Global Organizational Units > Cross-System Company Codes
a)     Cross-System Company Codes
b) Assign Cross-System Company Code to Chart of Accounts
c) Assign Company Code to Cross-System Company Code
Cross-system company codes are used in the distribution in financial accounting. There is exactly one central system for each cross-system company code in the distributed environment. One company code has to be assigned to this cross-system company code on each system involved in the distribution.
When sending an IDoc with company code-dependent data, the company code is replaced with the cross-system company code in all company code fields.
4)     IMG > Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Maintain Distribution Model and Distribute Views
Here we need a distribution model
     Structure: model view (call it XXXXXX)
               Sending system (AAAAAA)
                    Receiving system (XXXXXX)
5)     IMG > Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Predefined ALE Business Processes > Logistics > Master Data Distribution > Proposal for distribution model: Customer and vendor masters
(Beside of customers and vendors, we need to add the message type BOMMAT for material bill of materials and MATMAS for material master to to the distribution model, probably manually in step 4. Depending on further requests for automatic migration the one or other message type may need to be added later )
6)     IMG > Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Partner Profiles and Time of Processing > Maintain Partner Profile Manually
Partner profile type/Partner type: LS logical system
Partner profile/Partner number: XXXXXX
Details at Post Processing agent
Typ: US user
Agent: JJJJJ
Lang: EN
Outbound parameters
Message type:     ADDR2MAS
               ADR3MAS
               ADRMAS
               MATMAS
               CREMAS
               DEBMAS
Details per message type like this:
Receiver port: XXXXXXX Output mode: Collect Idocs and Do not start subsystem
IDOC type:      for     ADDR2MAS   use      ADR2MAS02
               ADR3MAS          ADR3MAS02
               ADRMAS          ADRMAS02
               MATMAS          MATMAS03
               CREMAS          CREMAS03
               DEBMAS          DEBMAS05
Activate syntax check
7)     Authorization needed to execute Transactions:
BD12 Send Customers
BD14 Send vendors
BD10 Send material
BD30 Send bill of material
Depending on future migration requests for other objects we may need some more.

File to IDOC (CREMAS03)

Hi Experts,
I am trying to load Vendor data in the R/3 system, I got stuck up when I am trying to do mapping between file and IDOC, how can get CREMAS03 Idoc into XI.... Please help
Thnx
Raj

Hi Raj,
You have to import the metadata for SAP Interfaces(IDocs,RFCs) into XI Repository before you can use them in the mapping.
You can import the Idocs into your own SWC but as a best practice, these Idocs were imported into SWCs like SAP APPL, SAP BASIS etc. In this way there is no duplication of these Interfaces in multiple SWCs.
To Import the IDOC metadata
1) Edit the SWC.
2) Make sure you have the "import of RFC and Idoc interfaces from SAP systems permitted" radio button selected with connection data for the backend R/3 system.
4) In the SWC, on the left panel select the Tab "Imported Objects". Provide the connection data if asked for. Select the Idoc CREMAS.CREMAS03 and import it.
5) This imported Idoc will be added to the list of Idocs in "Imported Objects" Tab. Verify the structure of the Idoc before using that in your mapping.
Hope this helps.
Regards,
Sam Raju

Idocs- not to overwrite client data

Hi all,
I am using CREMAS03 and I have an interesting requirement.
I am using file port, so on the load side I have a conversion program which manipulates idoc file and creates idocs from it.
The requirement is that I have to retain the basic data ie client level data ( like LFA1 , LFB1 etc) and extend views like LFM1 etc.
I tried with the MSGFN field but it didnt work.
Does anyone has any idea ?
Thanks & Regards,
Ankur

Hi Ankur,
Just a thought, since you say you have a conversion program that creates the IDOCs.
Can you read the client data of the vendor and fill the corresponding segments of your IDOC with the selected data and then use the file contents for the extended view data segments? Basically ignore what you are getting on the file as far as the client data is concerned, yet fill the corresponding IDoc segments from the database.
Hope this helps,
Srinivas

FIELD BNKA-XPGRO IN IDOC CREMAS03

Hi all
   In 46C, we populate IDoc cremas03 with data bank.
   When we entry the IDoc, an error occurs:
   "Field bnka-xpgro not allowed" .
   It occurs because we are sending this field and it   does not belongs to the screen.
   what can I do?
   Thanks

Check your config (IMG) settings if the field can be available for input.
Hope this helps.
Bipin

HOW TO SEND NUMBER OF ITEM DATA FOR ONE HEADER FROM SENDER TO RECEIVER ?

HI FRIENDS,
IF WE ARE SENDING A FILE TO IDOC ( SAP R/3. EX : CREMAS03). THEN HOW WE CAN SEND BANK DETAILS OF A VENDOR(TABLE CONTROL) TO RECEIVER IDOC(SAP R/3). PLEASE SEND THE SOLUTION WITH EXAMPLE( SCREEN SHOTS ALSO IF AVAILABLE)

Hi !
Check the E1LFBKM segment of the CREMAS03 idoc, it contains the banking data of the vendor.
Regards,
Matias.

Can we use idoc technique to change or delete the vendor master data?

Hi,gurus,
Can we use idoc technique to change or delete the vendor master data?You know we can create vendor data using idoc CREMAS03 as the receiver adapter,but when change or delete the specified vendor data,must we use RFC adapter technique?
Another question:I found the bapi which creates a vendor master data doesn't have the parameter account group,then we turned to idoc technique.But which adapter should I use when change or delete the vendor data?
Thanks in advance.

Hi,
>>>I found the field of the segment of deletion flag at different level,and very appreaciate your help.
yes - LOEVM - but remember this will not delete the record but only mark it for deletion
>>>It's a long time to wait for your new blog,what new and interesting things do you find?
at least 4 new in my head - 2 simple but important and 2 new + I'd also like to write something for XI guys about
BO data integrator which can also work as EAI tool (BTW I know it's ETL) but how knows when they will appear
Regards,
Michal Krawczyk

Cremas03 data??

Similar Messages

Maybe you are looking for