SARA Archiving Idocs and the retention period , RSEXARCB

Hi Experts
I am having few questions on the Idoc Archivng -
1. I want to know the safe retention period for Idocs , I am planning to do archivng of Idocs which are 60 days older or more. How to determine the exact period for Idocs that we can keep in the database tables and also in the file system. What will the exact time in tables and also in Filesystem before we copy to a tape.
2. About program RSEXARCB , I want to schedule automatic background job for only Idocs which are in status 3 and 53 using this program every week. In this program I dont see any variable or any selection field where I can select this options. Is there any other program in SAP where we can select this options?
FYI - We are on ECC 5.0
Thanks
Chandra

Hi,
Thanks for your reply please.
But while making changes to the retention period i am getting following message:
                                                                                Diagnosis
A retention period has been entered for a profile value category, that
    is shorter than that of the billing document headers.
This is an invalid entry, because you cannot archive profile values
    before billing document headers.
System Response
The system does not permit you to save the retention period combination.
Procedure
Correct the retention period for the profile value category or the
    corresponding billing document header category accordingly.
Please guide.
Thanks and Regards

Similar Messages

Archiving and different Retention period by specific interface

We want to specify different Retention period for different interfaces (audit reasons)... and based on search in SDN, it does not seem like this is supported by SAP...
Do any of you know if SAP intends to support this in future? Any ideas for overcoming this gap? or is this limitation deliberate (and has been kept in place for a reason)?

Hi Krish,
Actually I don't think we have this option of setting the retention period for specific interfaces,
but for the global interfaces in the system.
If you want to increase the time for Audit Log messages you need to change parameter 'messaging.auditLog.memoryCache' to false in order to persist the audit logs in PI 7.1 system. Take a look at note #1314974 for more details.
And notice that after changing the parameter to false, audit logs are persisted till the corresponding messages are deleted. The default retention period of messages on AE is 30 days, keep in mind that it could have a little impact on the data volume.
To increase the retention time in AFW, go to:
Services -> XPI Adapter: XI:
"xiadapter.outbound.persistDuration.default"
"xiadapter.inbound.persistDuration.default"
For the Integration Engine, it's under SXMB_ADM -> Integration Engine Configuration and Configuration.
Regards,
Caio Cagnani

How to change the retention period of os watcher log,

How to change the retention period of os watcher log, by default it is 7 days. but in our exadata env. automatically oswatcher logs are deleted , so i want to check the retention period.
Regards,
Ani

Hi Ani,
Go to :- /opt/oracle.cellos/validations/init.d/oswatcher
Open the file "oswatcher" file.check for the line "/startOSW.sh X Y Z". Where X is the snapshot interval
make the change and you are done
Regards,
Sunil Bhola

Archive purchase document log - Retention period not maintained

Hello Everybody,
   I have been trying to archive the Purchase document, I have also set the Retention period is 0 (Zero), but when i archive the some Purchase document, it is give log like that
Object                                                     Message
4700000053 00010                                           Retention period not maintained
4700000066 00010                                           Retention period not maintained
4700000079 00010                                           Retention period not maintained
So please suggest me how to solve the problem
Thanks

Solved, by archiving

After upgrading to Mavericks, all of my contacts disappeared. Did a "contacts archive" export and the file is 17mbs. Looks like there's data, but none of it at all displays. What gives? 20" iMac, early '09

After upgrading to Mavericks, all of my contacts disappeared. Did a "contacts archive" export and the file is 17mbs. Looks like there's data, but none of it at all displays. What gives? 20" iMac, early '09

After upgrading to Mavericks, all of my contacts disappeared. Did a "contacts archive" export and the file is 17mbs. Looks like there's data, but none of it at all displays. What gives? 20" iMac, early '09

I recently installed the trial version of Adobe XI and the trial period ended, so I wanted to revert back to the version I already had. I did not see any uninstall feature and my old version was apparently replaced by the trial version. I cannot re-instal

I recently installed the trial version of Adobe XI and the trial period ended, so I wanted to revert back to the version I already had. I did not see any uninstall feature and my old version was apparently replaced by the trial version. I cannot re-install a previous version b/c I need both a product Id (GOd only knows where that is now) and a way to uninstall the trial. Any ideas?

When you installed the trial, there should have been an option to have ignored your current installation and leave it. Apparently you skipped that case. To uninstall the trial (in Windows) go to Control Panel>Programs & Features and select the Acrobat XI and choose uninstall. After the uninstall run http://labs.adobe.com/downloads/acrobatcleaner.html to clean up your system. HOWEVER, if you see your old Acrobat in that window, do not run the cleaner, but do a repair on the old version.
You did not mention the old version you had. You might try from http://helpx.adobe.com/acrobat/kb/acrobat-downloads.html. As for the S/N, you should have register and if so you can get it from Adobe. The instructions are at http://helpx.adobe.com/x-productkb/global/find-serial-number.html#adobeproductdownload.
Be sure to backup any download of the old installer and the S/N to CD or backup HD for future use. They will not likely continue to be available.

Relation between an idoc and the workflow launched

Hi masters.
I have a hard question to solve.
I have an inbound idoc whick launch a workflow. Also i have a report to reprocess a workflow that has not finished or has finished with Error status.
But my requirement is that if the status of the inbound status is 68 you have not reprocess the workflow which has generated this idoc.
Do you know hoy i can obtain the data between the workflow and the idoc?
Many thanks.
<b><REMOVED BY MODERATOR></b>
Manel
Message was edited by:
Alvaro Tejada Galindo

Hi again Ferry,
Yes, but i need to do this with abap.
I have a report to reprocess workflows. I have only the id workflow and the status (table SWWWIHEAD) but i have to reprocess only the workflows which idoc (idoc that has generated this task) are not in status 68.
Many thx!!
Manel

CVA function and the year-period of acquisition

Hi,
Up to now we have booked the FV value manually in the SEM. In the course of FV booking we have used the year/period of acquisition and in special case the partner code. In the currency translation we have set up the special currency translation key in which the exchange rate applies directly from the implicit calculation. (This is the end of the period) It works.
We implement the CVA function in the SEM now. We customize some types of assets/liabilities, some FV differences, some tasks and document types in the CVA function.
Example:
If we have bought a new company, then generally the FV booking date and the acquisition date (the beginning date of valuation allowances) are different. The important for this is because we have to use the date of currency exchange which is same as the beginning date of valuation allowances. We get to know the final value of FV later than the date of acquisition of the company.
For example:
Unit: A
Date: 2010.12
The beginning date of valuation allowances: 2010.12
The date of capitalization: 2010.12
The original cost item u2013 acquisition:
Item: 21631
Movement type: 150
The original book value: 120 EUR
The currency exchange rate: 0,8
The bookings in 2010.12:
-     FV value- acquisition
-     Depreciation
-     Currency translation (the original book value in the group currency: 96 USD with 150 movement type)
Date: 2011.00
The opening value in the 21631 item:
000 movement type (opening movement type): 120 EUR u2013 96 USD (in the group currency)
050 movement type: 12 USD (in the group currency)
total value: 120 EUR u2013 84 USD (in the group currency)
Date: 2011.01
The beginning date of valuation allowances: 2011.01
The date of capitalization: 2011.01
The new original cost item u2013 acquisition:
Item: 21631
Movement type: 150
The new original book value: 20 EUR
The currency exchange rate: 0,7
The bookings in 2011.01:
-     FV value- acquisition
-     Depreciation
-     Currency translation (the original book value in the group currency: 14 USD with 150 movement type)
The original book value in the group currency in 2011.01 is not correct, the good value can be 18 USD with 150 movement type and 4 USD as difference u2013 050 movement type.
We have to use 2011.01 period as the beginning date of valuation allowances and the date of capitalization, because 2012.12 period is u201Cclosedu201D and we can not modify it, but the CVA is connected to the acquisition in 2010.12.
If we use 2010.12 period to the beginning date of valuation allowances and the date of capitalization the system does not book the acquisition in 2011.01. In this case we should use the year/period of acquisition. It follows the logic of the SEM.
It can be the good solution, if we can fill the field of beginning date of valuation allowances to 2010.12 in the 2011.01 year/period. After the modification we have received an error message with UCMA004 message number. (Capitalization follows the starting date of valuation allowances)
Or we would like to fix the year/period of acquisition in the CVA, in the original cost item u2013 acquisition, but it can not be, because the year/period of acquisition and the partner code fields do not appear.
If we book manually with this 21631 position, then we can fill the fields of the year/period of acquisition and partner code.
The breakdown category of 21631 item contains the following fields:
-     movement type
-     year of acquisition
-     period of acquisition
-     partner code
We do not change the currency translation, so we use the special currency translation key in which the exchange rate applies directly from the implicit calculation. (This is the end of the period)
Question:
- Why is not allowed the system, that the beginning date of valuation allowances can less than the date of capitalization?
- Why are not appeared the year/period of acquisition and partner code fields in the original cost item?
Best regards,

Thanks for the answers until now.
Surely a Day characteristic (ex. CA_DAY, derived from 0CALDAY) would work.
But we have this requirement in many other cubes (I posted only an example) and it's not feasible to create this characteristic now.
I understood the other suggestions, but the problem is not on selecting the values.
We have two restricted key figures, one for a period (filled by the users) and another one for this period - 12.
They work OK and bring the correct results.
The problem is on presenting the results, because as we have 0CALDAY in the line the results appear on two different lines.
Example:
15.07.2010    950,00
15.07.2011    980,00.
Is ther any way to present the results in the same line?
Example:
15.07.2011    950,00 (last year)     980,00 (today)
or
15.07             950,00 (last year)     980,00 (today)
or any other way?
César

Idocs and the application log

Hello there,
i have a general question. I am about to integrate idocs into an interface managing program and i wanted to know if idocs are known to use the application log for writing (error) messages.
I know they have the possiblity to do so, but i do not know if this is frequently used or even used at all. At least it is not on my system.
Thanks in advance for your answers.
Kind regards
Jonas Liebstückel

no, I am thinking this has to do with the IDOC-type - either you can flag the use of the application log somewhere in the IDOC-configuration or the processing funciton modules are doing it. I would have to dig around to find out, but so can you: just check along the WE* with MATMAS and look at the function modules that are behind the processing code ... WE41

Re: Retention Period, Residence time and Archiving Cycle

Hello Experts,
1.Could someone help me where we maintain the retention period, residence time and archiving cycle for an archiving object.
2.How to schedule a background job for archiving???
Regards
RR

Hello RR,
Residence period: Most of the archiving object residence period is maintained in customizing > Application specific customizing in Archive development tool access through transaction SARA.
Note: There are some archiving object for which you can't maintain residence period however these archiving object residence period should be manually controlled in write variant.
Retention Period: This retention period is mentioned in archive server.
Total retention time = Online Residence period + Offline Retention period.
2. You can schedule archiving jobs by SARA transaction. This transaction will help in scheduling the job background. Or By using Background user id, one can schedule the archiving jobs by background.
-Thanks,
Ajay

Inbound IDOC messages Retention Period- Where to Check

Hi Gurus,
Where do we specify Inbound IDOC messages rention period.
In our system I do not see Inbound IDOC messages ( coming from ECC to PI) older than 15 days.
But I see Outbound IDOC messages ( PI to ECC) older than 15 days.Also I see non IDOC messages older than 15 days.
I checked in SXMB_ADM, Integration Engine Configuration and I do not see any parameter for IDOCS.
I appreciate any pointers.
Regards,
Ramesh.

Hi,
As far as I know, there is no specific setting for IDOC mesages .
Retention period is generically set for all the messages in XI.
Inbound and outbound messages are always with respect to ECC and not PI.
(What you call inbound are actually outbound and vice versa).
Retention periods, can be viewed using SXMB_ADM transaction only.
Regards,
Ravi Kanth Talagana

Archive RETENTION Periods Configuration..

Hi All,
I am trying to do the Archiving for my XI system and I got configured my system in this way below.
I just want to know my configuration is correct or not. I am not sure about the retention period given is correct or not. Configuration is not good can you correct me.
Category     Parameters                                      Subparameters Current Value Default Value
ARCHIVE        PERSIST_DURATION                 ASYNC     1     1
DELETION     PERSIST_DURATION                 ASYNC     1     1
DELETION     PERSIST_DURATION                 HISTORY     60     30
DELETION     PERSIST_DURATION                 SYNC        1     0
DELETION     PERSIST_DURATION_ERROR                 SYNC                 1     1
Retention period
Retention Period for Asynchronous XML message in the Database
XML Messages Without Errors Awaiting Deletion      1
XML Messages Without Errors Awaiting Archiving     1
Retention Period for Synchronous XML message in the Database
XML Messages with Errors Awaiting Deletion         1
XML Messages Without Errors Awaiting Deletion      1
Retention Period for History Entries in the Database
History Entries for Deleted XML Messages          60
This is my situation to keep and run my Archive job and Deleted jobs:
I want to keep my XML messages in the SXMB_MONI for 60 days and I need to delete the XML message is older then 60 days need to archive and delete.
For example current date is 02/26/2008 to 12/29/2007 is the 60 days and earlier need to be deleted.
Everyday I need to Archive job and everyday I need to delete the archived messages more then 60 days.
1.     Schedule Archiving job
          (SAP_BC_XMB_ARCHIVE_111) I gave it to execute everyday 2:00AM.
2.     Schedule Delete job
                1.     Schedule Delete job for XML message
                       (SAP_BC_XMB_DELETE_111) I gave it to execute everyday 4:00AM
                 2.     Schedule Delete job for History message
                      (SAP_BC_XMB_HIST_DELETE_111) I gave it to execute everyday 5:00AM.
Once I execute this archive jobs I can see this and it was executed perfectly and I see all my messages got deleted and I can see only todays message in SXMB_MONI.
Help to resolve this issue with keeping all the 60 days message in my sxmb_moni.
Different issue: In my SXMSPMAST table I can see some of the XML messages are marked as DEL in the field ITFACTION. How I can change this DEL to ARCH.
Thanks,
Jane

Dear Jane,
I had a look at the configurational settings and the desired behavior of the Integration Server. Most likely there is a misunderstanding of one parameter which leads to the untimely deletion that you have observed.
You state that you set the retention period for history entries to 60 days and you want to keep the messages in technical monitor (SXMB_MONI) for 60 days, too.
Please note that 'history entry' does not denote a complete XML message. The history entry is kind of a fingerprint of a message that is used for duplicate detection. Keeping the fingerprints does not mean keeping the messages!
If you want to see XML messages in technical monitor for 60 days we have to distinguish between messages flagged for deletion and messages flagged for archiving:
- deletion: the only way here is to set the retention period to 60(DELETION PERSIST_DURATION ASYNC=60). This is the only possibility to ensure these messages are visible in technical monitor for this period of time.
- archiving: here it is important to know that archiving works in two steps. Firstly the messages are written to file. Secondly the file is read (to ensure data integrity) and XML messages are deleted. You can decouple these two steps, i.e it is possible to run archiving for asynchronous messages after 1 day. Then the messages are still available in SXMB_MONI as the delete step is pending. This deletion can be run 59 days after archiving. However, I strongly recommend to not use this option. Instead please set the retention period for these messages to 60 days, too (ARCHIVE PERSIST_DURATION ASYNC=60). Configure the deletion step to be executed immediately after archiving (TX AOBJ). Additionally configure the reorganizational jobs to be executed daily as you have lined out.
Regarding your second issue: unfortunately it is currently impossible to change the action to be taken on a message from 'deletion' to 'archiving' belatedly. Please be aware of the fact that OSS note 789352 applies to XI2.0 only. I strongly advise against applying this note to any release higher than 6.20.
To give you an outlook: SAP is working on a general tool for belated changing of the interface action. The decision was made to deliver this functionality as part of PI7.01 EHP1 and PI7.11 EHP1. It is not yet clear whether this tool will be downported. If it is downported it will probably shipped as part of the next support packages (XI3.0 SP22 / PI7.00 SP16 / PI7.10 SP6).
Best Regards,
Harald Keimer
XI Development Support
SAP AG, Walldorf

What is IDOC and ALE?

Hi anybody,
         Please tell me what is IDOC and ALE? What pupose using IDOC and ALE?
          Give me Example sample code of using IDOC and ALE.
Thanks
S.Muthu.

Dear,
Here is some facts which will be helpful to clear yr concepts for ALE/IDOCs.
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.
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.
*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.
ALE (Application Linking and Enabling)
Ale Technology is SAPs technology to support distributed yet integrated processes across several SAP systems.
Distributed Process:
A distributed process is one in which part of a business process is carried out on one system and part on another. The two systems would exchange data with each other at appropriate points to stay synchronized.
Need for Distributed Process:
Business in Different Geographical Locations.
Non availability of dedicated network.
Cultural and language differences in Geographical locations.
Running of Mission-critical Applications (Like Maintenance downtime etc.).
Separate up gradation of Modules.
Distributed SAP SYSTEM CHALLENGES
A system that understands the syntax and semantics of the data. It was important from the very beginning to base the distribution of data on business rules, not on database replication techniques.
Distributed systems that can maintain their autonomy while being integrated as one logical SAP system. The systems should be able to operate independently and support logical processing of transactions and data.
Distributed systems that can handle different data models. A local implementation should be able to customize the system to meet its local needs.
Receiving systems that can handle their own problems and not tie up the sending system.
Systems that maintain continued operation in spite of network failure. Changes made to either system should be synchronized after the network connection is restored.
A sound technology and methodology that can be used in all distribution scenarios.
SAP Distributed environment:
ALE allows for efficient and reliable communication between distributed processes across physically separate SAP systems.
ALE is based on application to application integration using messaging architecture. A message defines data that is exchanged between two processes. IDocs are containers that hold data exchanged between the two systems.
Benefits of ALE:
Integration with non-SAP systems: ALE architecture allows third party applications to integrate with SAP system.
Reliable Distribution: Once message type created and the receiver of the message is determined, ALE delivers the message to the recipient. If there is any network problem it will buffer the message and delivers the message once the network is restored. It also ensures that the message is not delivered twice.
Release Upgrade: Any of the distributed system can be upgraded to the new release of SAP without affecting the functionality. The ALE layer ensures backward compatibility of messages exchanged between systems.
ALE Architecture:
It consists of an Outbound process, an Inbound process, and an Exception Handling process.
Outbound Process:
ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.
1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.
2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.
3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.
4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.
Inbound Process:
The inbound process receives an IDoc and creates a document in the system.
1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.
2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.
3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.
IDoc Types:
IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
An IDoc is an instance of an IDoc Type and consists of three types of records.
i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
Message in IDoc Type:
A Message represents a specific type of document transmitted between two partners.
Outbound Process in IDocs:
Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
The Customer Model:
A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
Message control:
Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the
application logic.
Change Pointers:
The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
IDoc Structure:
A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
Selection Program:
Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection programs design depends on the triggering mechanism used in the process.
Filter Objects;
Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
Port Definition:
A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
RFC Destination:
The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
Partner Profile:
A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDocs packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
Service Programs and Configuration Tables:
The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
Process flow for Distributing Transactional Data:
Transactional data is distributed using two techniques: with Message control and without message control.
Process flow for Distributing Master Data:
Master data between SAP systems is distributed using two techniques: Stand alone Programs and Change Pointers.
Triggering the Outbound Process via Stand-Alone Programs:
Stand-Alone programs are started explicitly by a user to transmit data from one SAP system to another. Standard Programs for several master data objects exist in SAP. Ex. The material master data can be transferred using the RBDSEMAT program or transaction BD10.
The stand-alone programs provide a selection screen to specify the objects to be transferred and the receiving system. After the stand-alone program is executed, it calls the IDoc selection program with the specified parameters.
Triggering the Outbound Process via Change Pointers:
The change pointer technique is used to initiate the outbound process automatically when master data is created or changed.
A standard program, RBDMIDOC, is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process for distributing the master data to the appropriate destination. The RBDMIDOC program reads the table TBDME to determine the IDoc selection program for a message type.
Processing in the Application Layer:
The customer distribution model is consulted to make sure that a receiver has been defined for the message to be transmitted. If not, processing ends. If at least one receiver exists, the IDoc selection program reads the master data object from the database and creates a master IDoc from it. The master IDoc is stored in memory. The program then calls the ALE service layer by using the function module MASTER_IDOC_DISTRIBUTE, passing the master IDoc and the receiver information.
Processing in the ALE Interface Layer:
Processing in the ALE Layer consists of the following steps:
Receiver Determination: The determination of the receiver is done through Customer Distribution Model.
IDoc Filtering: if an IDoc filter is specified in the distribution model for a receiver, values in the filter are compared against the values in the IDoc data records. If a data record does not meet the filter criteria, it is dropped.
Segment Filtering: For each sender and receiver combination, a set of segments that are not required can be filtered out.
Field conversion: Field values in data records are converted by using the conversion rules specified for the segment.
Version change for segments: Segments are version-controlled. A new version of a segment always contains fields from the preceding version and fields added for the new version. Release in IDoc type field of the partner profile to determine the version of the segment to be generated.
Version change for IDocs: IDocs are also version controlled. The version is determined from the Basic Type field of the partner profile.
Communication IDocs generated: The final IDoc generated for a receiver after all the conversions and filtering operations is the communication IDoc. One master IDoc can have multiple communication IDocs depending on the number of receivers identified and the filter operations performed. IDoc gets the status record with a status code of 01 (IDoc Created).
Syntax check performed: IDoc goes through a syntax check and data integrity validation. If errors found the IDoc get the status of 26 (error during syntax check of IDoc Outbound). If no errors found the IDoc gets the status 30 (IDoc ready for dispatch ALE Service).
IDoc dispatched to the communication Layer: In the ALE process, IDocs are dispatched using the asynchronous RFC method, which means that the sending system does not await for data to be received or processed on the destination system. After IDocs have been transferred to the communication layer, they get a status code 01 (Data Passed to Port OK).
Processing in the Communication Layer:
To dispatch an IDoc to a destination system, the system reads the port definition specified in the partner profile to determine the destination system, which is then used to read the RFC destination. The RFC destination contains communication settings to log o to the remote SAP system. The sending system calls the INBOUND_IDOC_PROCESS function module asynchronously on the destination system and passes the IDoc data via the memory buffers.
Inbound Process in IDocs:
An inbound process used IDoc structure, posting programs, filter objects, conversion rules, a partner profile, service programs, and configuration tables to post an application document from an IDoc.
Posting Program:
Posting programs, which are implemented as function modules, read data from an IDoc and create an application document from it. A posting program exists for each message. Each posting program is assigned a process code. A process code can point to a function module or a work flow. In the standard program process codes always point to a function module.
Ex. The posting program for message type MATMAS is IDOC_INPUT_MATMAS which has a process code MATM.
Workflow:
A workflow represents a sequence of customized steps to be carried out for a process. The workflow management system is used to model the sequence, identify information required to carry out the steps and identify the person responsible for the dialog steps.
Partner Profile;
A partner profile specifies the components used in an inbound process (partner number, message type, and process code), the mode in which IDocs are processed (batch versus immediate), and the person to be notified in case of errors.
Process flow for the Inbound process via a Function Module:
In this process, IDocs are received from another system and passed to the posting function module directly.
1. Processing in the communication Layer:
The IDOC_INBOUND_ASYCHRONOUS program, triggered as a result of an RFC from the sending system, acts as the entry point for all inbound ALE processes. The IDoc to be processed is passed as an input parameter. Control is transferred to the ALE/EDI layer.
2. Processing in the ALE/EDI Interface Layer:
Basic integrity check: A basic integrity check is performed on the control record.
Segment Filtering and conversion: Filtering out unwanted segments and carry out any required conversion of field values.
Creation of Application IDoc: The application IDoc is created and stored in the database and a syntax check is performed. If there are errors it gets status code of 60 (Error during Syntax check of IDoc Inbound). At this point a tangible IDoc, which can be monitored via one of the monitoring transactions, is created and the IDoc gets status code 50 (IDoc Added).
IDoc Marked ready for Dispatch: IDoc gets the status code 64 (IDoc ready to be passed to application).
IDoc is passed to the posting program: The partner profile table is read. If the value of the Processing field is set to Process Immediately, the IDoc is passed to the posting program immediately using the program RBDAPP01.
3. Processing in the Posting Module:
The process code in the partner profile points to a posting module for the specific message in the IDoc. The posting program implemented as a function module either calls a standard SAP transaction by using the Call Transaction command for posting the document or invokes a direct input function module.
The results of execution are passed back via the function modules output parameters. If the posting is successful IDoc gets the status code 53 (Application Document Posted) or it gets status code 51 (Error: Application
How to create idoc?
*WE30 - you can create a IDOC type
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
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
This report creates IDocs from the change pointers for the specified message type. It then sends them to the receiving system and flags the change pointers as processed in respect of the specified message type.
The receiving systems for the specified message type are determined from the customer distribution model.
Output:-The report outputs information about the number of master IDocs and communication IDocs created.
RSEOUT00 Process all selected IDocs (EDI) Report for generation of files for EDI outbound processing.The report processes the IDocs available in the system with the status 'to be processed'. The IDocs are selected according to the selection options and parameters specified.
It is important that you make sure that only test messages or productive messages are selected.
The IDocs are processed in various files for various output modes and for various ports. The names of the files are created according to the naming definition for the outbound file. This definition is determined in the port definition.
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.
Hope This will be helpful,
Best Regards ,
P Singh

SXMB_MONI retention period

Hi all,
I configured the retention period for deleting and archiving XML messages in SXMB_ADM.
My retention period for deleting messages is 30 days and the job is scheduled on a weekly basis.
When I go to the message monitoring in the RWB, I can see that all messages older then 30 days are deleted.
However when I go to SXMB_MONI I'm still able to see all messages.
In the persistance layer analysis, I see that the table keeps growing and currently is over 90%.
Does anyone know how I can remove the message out of the SXMB_MONI??
Kind regards,
Steven

Dear Steven,
you might have a look at OSS note 872388 'Troubleshooting Archiving and Deletion in XI 3.0' that provides a comprehensive collection of common issues regarding archiving and deletion. Please walk through section 5 'Troubleshooting Archiving / Deletion of XML messages and history entries in the Integration Server'.
You stated that 5-8% of all messages are deleted through running the deletion job. This indicates that you are not using table switch procedure, ruling out 5-i).
However, 7/30=23% of the messages should be deleted (provided that the message volume is constant over time). Often step 5-k)-2 (adapter status update missing) turns out to be the reason for not deleting XI messages. For the sake of completeness I recommend to have a look at entire section 5.
Best Regards,
Harald Keimer
XI Development Support
SAP AG, Walldorf

How to view archived IDoc's

Hi experts,
i need to view the archived content of the archived idocs. i tried with SARI(Infostructure SAP_IDOC_001),
but i cant view the content of the archived IDOC's. the scenario is like,
> IDoc's are archived using SARA
> Delete that IDOC using SARA
> SAP_IDOC_001 infostructure got activated using SARI
after that i tried to view the content in WE10, but i cant. Is thr any other steps i missed here?
Plz help on this.
Thanks,
murugan.

Hi,
After activating Infostructure, Did you build the Info structure? If not then build it.
Path > SARI > Customizing > Status > Build structure > Select the Archive file and run it.
Note: After successfull execution the archive file will have green signle.
Then you can display the archived IDOC's
Hope this will help you.
-Thanks,
Ajay

SARA Archiving Idocs and the retention period , RSEXARCB

Similar Messages

Maybe you are looking for