Issue:Creation of Extended iDOC data entries in receiving system.

Hi all,
I have extended standard IDOC MATMAS05 for classification view.I am receiving the data successfully on recewing side.And i have done coading in user exit to store data in database table inside
IDOC_INPUT_MATMAS01- function module.
When i execute the BD10 from sending sytem and view the idoc at receiving end from WE05 i can see the idoc but when i try to see the material i cant see the classification(extended) view in mm03.Rest of the views are created .When i execute the idoc from WE19 ,Classification(extended) view gets created.
Please guide me so that the CLASSIFICATION view get automatically created in receiving system without using WE19.
Thanks.

Yes i used this function module-
CALL FUNCTION 'BAPI_OBJCL_CREATE'
              EXPORTING
                objectkeynew            = objectkeynew1
                objecttablenew          = 'MARA'
                classnumnew             = wa_classnumnew1
                classtypenew            = z1sklart-klart              "classtypenew1
                status                  = '1'
STANDARDCLASS           =
CHANGENUMBER            =
                keydate                 = sy-datum
NO_DEFAULT_VALUES       = ' '
IMPORTING
CLASSIF_STATUS          =
              TABLES
ALLOCVALUESNUM          =
                allocvalueschar         = allocvalueschar2[]
ALLOCVALUESCURR         =
                return                  = return1
*WAIT UP TO 1 SECONDS.
            CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
             EXPORTING
               wait          = 'X'
IMPORTING
RETURN        =
Please explain me how to maintain the Views Status at MARA general info segment level.

Similar Messages

How does IDOC data transfer happensbetween two system?

Hi,
If there are data in system A and I need to transfer to system B using IDoc.
What are the key things which will enable data transfer from system A to system.
It would be great if someone can explain how does IDOC data gets transferred from system A to sytemB.
Regards,
Rachel
Moderator Message : Search for available information or Read SAP documentation. Thread locked
Edited by: Vinod Kumar on Apr 26, 2011 12:37 PM

thanks for all your replies...
let me write down what i have understood ..plz correct me if i have not followed properly..
1) Once IDocs successfully reach R3 , a function module specific to the Idoc type is called "<b>automatically</b>" and updates database...
2) this function module we specify in the process code while creating partner profiles
basically all we need to do is to specify correct function module, right?
the rest of the process ie . updation in the tables(database) is done automatically..
Once database is updated, where can i see the added/updated records in database?
also how do we find this function module?
I am using MATMAS05...
Regards,
Roshani

Time out when seinding Idocs from XI to receiving system

Hi All,
we have implemented a file to Idoc scenario in our XI test environment.
When sending more than one file at a time (containing one record -> 1 Idoc after conversion) XI creates the Idocs but gets a time out when passing the Idocs to the receiving SAP 4.6C system. We find the messages blocked in transaction SM58 with the status message "Transaction recorded" and on the XI system short dumps are created with the time out error message.
Does anyone know this problem and can give us some hints how to resolve it ?
Thanks in advance,
Christiane

Christiane,
Check your partner profiles in the target R/3 system. Use Tcode WE20 and check the inbound parameters option to see if the radio button 'Process Immediately' is switched on. If yes, change this to 'Process by background program'.
This way, the IDOC will be created in your system with status 64. You can then use program RBDAPP01 in the R/3 system to post these IDOCs to application.
The reason I say this is, sometimes, posting applicaitons may take a long time thereby resulting in timeout. If this is not the actual reason, atleast this will lead you to the correct problem.
Try this and let me know what's happening.
KK

Same idoc to multiple EDI receiver system using rule

Dear Friends!
Good day! I am using desadv.delvry03 idoc and I want to send same idoc from same communication component to multiple receiver parties without mapping.
I have created first scenario successfully using idoc, when I create another scenario it gives me message like "Object already exist" . for that I have to use Service interface. I dont want to use service interface for this purpose. In my scenarios mapping is not even required. one idoc to and multiple receivers thats it.
Can you please guide me how to do the above requirement ?
your any help will be appreciated greatly
Thanking you
Regards
Dipen

Hi,
For this... U can create 1 sender agreent for that idoc if necesseary....otherwise we dont required IDOC sender Agreement.
Then Create 1 reciver determination in that u can mention the 2 recivers details...
same thing for interface determination also.
and finally create 2 reciver agreement and 2 reciver communication channels for 2 systems.
Let me know if you require any further information.
Thanks,
Sreenivas

Change IDOC Control Record in Receiver system

Hi Guys,
I want to change the inbound IDOC control record,is there any BADI or F.M available ?
My scenario : XI to SAP and its a custom application.
Regards,
Rajesh.

hi Rajesh,
You can refer this wiki link , this will help you out in your problem
https://wiki.sdn.sap.com/wiki/display/ABAP/IDOC+Steps
Regards
Saurabh Goel

IDOC processing inbound in receiver system , transaction WE57

Hello,
possibly a simple question for those who are familar with IDOC processing.
In transaction WE57 you can add function modules for processing IDOCs e.g. inbound IDOCs.
Now I see in our system that there are two function modules added to the same IDOC.
Example Basis type MATMAS03:
Function modules: IDOC_INPUT_MATMAS01 and IDOC_INPUT_MATMASMDM.
We want to add an individual mapping on receiver side (not on XI, because it has to be accessible to a user group on receiver side to change required field contents sometimes) for fields which are empty.
My idea is that we can add a func.module here in WE57 for this purpose. But what about the existing two FMs?
Will they be processed in a sequence so that we can add more FMs to the same IDOC type?
Or should I replace one of them with a Z_IDOC_INPUT_MATMASxxx by copying it and adding the required functionality?
Any help is appreciated!
Regards
Dirk

Hi Dirk,
Will they be processed in a sequence so that we can add more FMs to the same IDOC type?
I dont think ....
BTW you would get better response if you post the question in ABAP forum.
https://www.sdn.sap.com/irj/sdn/abap-forums
Regards,
Sumit

Data entry issue in CATS

Dear All,
when i enter time (hours) in data entry sheet.. system says "Enter relevant working time attributes" I really dont know where i have done mistake.
Im using fields Pernr.name,controling area, tasklevel, task type, task component and attendance/ absence type in data entry sheet.
when i enter time only with controling area and attendace type, its accepting the time data but if i assigned task leave, task type and task component, then only system thooughing an error msg "*Enter relevant working time attributes".
I have checked all asignement with task type,tasklevel and task component.. which all ar correct but i dont knw why this msg coming..
can any one help me???
thanks,
Manjula.

Hi Manju..
I think there is an problem in tasktype component.. check whether you have activated 'component task type 'activated or not.. if you activated the check box.. then you just maintained abbsence / attendance type or wage type and also check the default vaule in the profile settings.
try and let me knw..
Dinesh.

Error in creation of PurOrd IDoc

Hi All,
I have set up the output type for PO and created patner profiles and also add the message types ORDER and ORDCHG but when I save the PO and check the messages, I get an error: " No recipient found for message type ORDERS in the ALE Model ".
What could be the possible problem?
Highly appreciate any kind of help.
Thanks in advance,
Shweta
PS: <b><REMOVED BY MODERATOR></b>
Message was edited by:
Alvaro Tejada Galindo

Hi
Check the Partner Profile in WE20 correctly
also see the steps for it as per the doc
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction 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 it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
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
Create Message Type
Go to transaction 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
Go to transaction 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
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
>>>> SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
Regards
Anji

Passing Changed extended fields using ALE-IDOC to receiving system

Hi all,
Please tell me how passing changed extended fields using ALE-IDOC to receiving system can be achieved. Is it possible by Chnage pointer concept.Do i need to do some coading after data enters into receiving system as it is required while creating the entries in database table.
For ex. in matmas05 extended for classification and inspection view and then created using 'CREATION'
related bapi.Do i also need to incorporate the changes by change related bapi or ir can be handled by change pointer concept.
Thanks.

Hi Sanu
1) Please tell me how passing changed extended fields using ALE-IDOC to receiving system can be achieved. Is it possible by Chnage pointer concept.
=> Looks like you have extended standard IDOC here. so you need to find User Exit or BADI for the Push program to populate the additional fields. Yes, it is possible thru change pointers as well.
1) Do i need to do some coading after data enters into receiving system as it is required while creating the entries in database table.
=> Yes, as suggested in 1 try finding User Exits/BADIs.
Regards
Shital

Where will be the IDOC data saved when the receiving system is not ready

where will be the idoc data saved data when the receiving system is not ready

Hi karthik,
If the receiving system is not ready ,
the data is to be transferred and function modules to be invoked are temporarily stored in tables ARFCSSTATE and ARFCSDATA. once the receiving system is ready , the entried in these tables wiil be deleted.
regards,
Prasad kodi.

Extracted Data size in sender system

Hi,
How to we know the size of the extracted data is sender system before loading data into the receiver system? Which phase in TDMS tree would provide us details?
Thanks.

Hi,
In order to get an approximate data transfer volume,
First you will have to enable Size Prediction in activity "De- / Activate Size Prediction for Receiver System" in System Analysis Phase.
Then, post running of the optional activity "Fill header tables (Collective Exec.) (Optional)", we have an activity "Display Data Transfer Volume (Optional)" which would show the approximate data that would be transferred to your target system
But note that this would mean extra runtime since the optional Fill Header Activity too would need to be executed.
Regards,
Suman

"Start Deletion of Data in Receiver System" does not start

I faced the problem tha data deletion in Receiver system is not started in TDTIM synario.
I started the activity "Start Deletion of Data in Receiver System" , the job "CNV_TDMS_09_RESTART_JOBS" is aborted till the job "CNV_MBT_CNV_TDMS_09_START_JOBS" is over in Receiver System.
The error message is "No log was created for object CAGTFBS and sub-objekt SLOMBT".
After The job "CNV_MBT_CNV_TDMS_09_START_JOBS" is over, the job "CNV_TDMS_09_RESTART_JOBS" is finished normaly but the no deletion job is released.
I carried out some deletion job by manual operation but other deletion job is not released.
Does Anyone knows the solution of this problem ?
Version:TDMS3.0 SP17
Basis: 700
Susumu

Hi Joerg,
Thank you for your reply.
> Please check the syslog for any reference to bad defined batch jobs! (all on receiver)
Syslog is nothing in receiver system.
> Is there any deletion job that can not be startet manually on the receiver side?
> (So normally on top of the list of scheduled deletion jobs.
I think all deletion job can be started manually.
Nomally, some deletion job is finished, the job is released next deletion job but no deletion jobs is released.
In addition, If rerun job "CNV_TDMS_09_RESTART_JOBS" is finished, no deletion jobs is released.
Best regards,
Susumu

Creation Of Custom Transaction For RF enabled devices "mobile data entry"

Hello Everyone,
i need some information, or some material or some example's for creating custom transactions that will invoke the standard good issue transaction of sap from the handled device using the RF , so can anybody give some reference which will help me in creating custom transaction for a RF enabled handled device, which will invoke the standard sap goods issue transaction( mb1a) ,, there are some LM-transaction which do goods issue from the RF enabled handled device, but in my case i want to do goods issue using reservation as my input, so can anybody guide me or send some reference material matching to my problem, i would really appreciate it..
thanks in advance...
sapient2006

Hi Hussaini,
Here are the steps.
1> Customization needs to be completed in SPRO. Logistics Execution -> Mobile Data entry section. Also compare entries with LM01 for understanding.
2> In the 'Define menu management', you can create dynamic menus. For Menu or transaction type, if you enter "1", a menu appears; if you enter "2", a transaction appears. Custom transactions can be created and assigned here.
Once that is done, when you execute LM01 you will see your custom transactions come up. Make sure that these are created keeping in mind the RF device screen size and limitations.
Regards,
Anand.

Creation of New Message Type for Extended IDoc

Dear Friends,
I want to create New Message Type for MATMAS and want to Active Change Pointers accordingly. Thru this Message Type how can I able to use Extended IDoc which I have created for Basic Idoc Type MATMAS05.
I am Sending Data from SAP to XI ; Any one can help me in this How can I create the Message Type with the IDoc Extn .
for Change Pointers.
Warm Regards,
Naveen Mutyapu.

Hi naveen mutyapu,
see these links
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
http://www.allinterview.com/rss/interview-questions/new/SAP-ALE-IDocs.xml
happy learning.
thanks
karthik

SM58 - IDoc adapter inbound: IDoc data record table contains no entries

Trying to send Idocs from SAP ECC6.0 via PI 7.0 up until 2 days ago there was no problem.
Since yesterday, only one specific type of Idoc does not make it into XI (PI). In the Idoc monitor (WE02) the idocs that were created gives status 3 which is good. But all Idocs of that specific type (ZRESCR01) does not go to XI. I can only find them bakc in SM58 where it gives the following message:
IDoc adapter inbound: IDoc data record table contains no entries
I have checked SAP notes 1157385 and also 940313, none of them gives me any more insight into this error. I have also checked all the configuration in WE20, SM59, and in XI (repository and directory) and in XI IDX1, IDX2 but could not find anything that would cause this. I can also not think of anything that changed since 2 days ago.
Please point me in the right direction.

hi,
i think in sm 58 u can find entries only when there is some failure in login credential .
if there is change in IDoc structure than you have to reimport the idoc metadata defination at IDX2.otherwise not requird.
please check the logical system name pointing to the your requird target system....
please also verify thet your port should not be blocked.
pls find the link it may help
Monitoring the IDOC Adapter in XI/PI using IDX5
regards,
navneet

Issue:Creation of Extended iDOC data entries in receiving system.

Similar Messages

Maybe you are looking for