Activating the IDOC Creation Process

How or Where should I configure that an IDOC needs to be created followed by the Creation of the application document?
Thank You.

Hi Jenni,
you need help of your functional consultant at every point so that you can clearly determine your application defnitions and configuration.
1. Go to transaction NACE. There you can see all the generic applications listed. Find out the one relavant to your idoc type from the functional person. If you select your relavant aplication, and click on the "Output types", you will see a list of all the output types for each business transaction defined for that application.
2. Again, ask your functional consultant, as to which output type is configured for your business transaction. Select that output type and go to "Processing routines".
3. There you will be able to see different ways in which the idoc can be triggered. Most of the time , we use processing routine "A (Distribution (ALE))". There you will also see the report which will trigger the idoc.
4. All the above mentioned customization is to be done by the functional consultant (or by technical after strictly seeking the permission). Once the output type is set, you go to the business application which is triggering your idoc and assign the output type & process it.
Also, you can configure the output type so that it will be created and processed automatically once the document is created. you can check with your functional consultant for the same.
Regards,
Selva K.

Similar Messages

Goods Confirmation - Idoc creation process???

Hi,
I see that during the goods confirmation process the idocs are created. well i'm aware of the ale configs but my question here is how there idocs are created and which is the process that initiates this...bascially i wish to extend the GR idoc in SRM with added segments but need to know where i got to write the code for the extended segments. this process of idoc created is seen during the call of the work flow WS10400010 but looking into this workflow i cannot see any steps that handle the idoc creation....
nb: my confirmation process happens without an approval step in between.
any thoughts on how to check the process that creates this idoc for confirmation?

Duplicate Question from SRM General Forum. It is answered, pls. close the thread. Thanks.
http://forums.sdn.sap.com/thread.jspa?threadID=2134619&tstart=0

Incorrect data after activating the request through Process chain.

Dear SDN chaps.
Today morning. I encountered a strange issue in DSO..
I have DSO which is updating from the AL11(application server) flat file.
While i am loading it to PSA there were no issues and after loading it to the DSO there is no issue and its passing through the routine and the data is populating properly in NEW data Table .But after successful activation of the request through process i am getting the wrong records in active data table.
Then i deleted the request and reran it manually i mean triggered the DTP and ran the manual activation surprisingly accurate records are coming through manual process..
I am just wondering why it is not working through process chain and why it is showing incorrect records through process chain execution and how it is showing accurate records through manual uploading process..'
Could some one please help to come out from this..By the way mine is SAP BI 7 SP20 &SP05 for BW 7.01
Thanks
K M R

Hi Pra
Thanks for your response..
We are doing PSA deletion and then we are uploading the data to PSA as well as DSO.
Now the issue is not in the part of loading we are facing the issue in Actiation of request if i am executing the activation through process chain it is sucess but the values are incorrect. If i am doing the manual activation it sucess with correct data.
Even i tried with a new chain but still i am facing the issue.
Surprise thing is in new data table the data is perfect in both the ways like manual upate and Process chain update only during activation i am getting incorrect record in the active data table..
Appreciate your help on this....
Thanks
K M R
Edited by: K M R on Jul 9, 2010 11:09 AM

How to restrict the idoc creation based on the distribution model

Hi all,
I want to create the idocs for certain material types only, for this i configured Distribution model and set the filter for material types.
If the delivery is created with the material type which is not in the filter means,
Idoc is creating for that Delivery with header segments only and restricting Item level segments.
it is coming to XI and failing in mapping every time.
I do not want to generate the whole idoc itself. Am i missing any thing??
Regards
Edited by: Suman gupta on Jun 10, 2010 11:13 PM

Hi Mike,
>>config in PI in the routing condition - if no lines exits don't send the message to the mapping/receiver
If no lines exists we can restrict don't send to receiver, but how can we restrict dont send to mapping??
It comes to mapping and failing in PI MONI.
Is there any way that i can restrict the Idoc generation itself in ECC ??
Regards

Automate the Idoc monitoring process

Hi,
As we do not use Solution Manager to monitor Idocs in R/3 system, we need to develop the customized report which will send a mail alert with the Idoc status on daily basis. Please suggest various effective approaches to develop this scenario.
Thanks.
Moderator message: please do some own research before asking.
Edited by: Thomas Zloch on Feb 21, 2011 2:02 PM

There are some standard reports which are already available. I could find a report RSEIDOCA, this sends mail based on the workflow. Please check if this is useful or it can be extended to meet your requirement.
Regards
Ranganath

Can u explin the IDOC creation with ALE/EDI step by step .

can you provide detalied code for i doc creation

hi
good
Do the following steps, idoc will trigger automatically.
If you need additional logic you have write user exit.(for first step you don't need coding).
Go to NACE and select V2 and click output type from menu.
Give following value.
Condition component Value
Access sequence 0005 (sales organization/customer)
Condition 0 (no condition)
Exclusive select
Output type LAVA (shipping notification outbound)
Procedure V10000 (shipping output)
Application V2 (shipping)
Processing subroutine Program RSNASTED,
form routine EDI-PROCESSING
General data Select Condition access and Multiple sending of output, otherwise
leave the fields blank
Time e.g. 4 (immediately, IDocs are generated immediately after
posting)
Transmission medium 6
Partner function WE
Language DE (German)
You must maintain following values for outbound partner profile.
Message type : Desadv
Partner type : Ku
Partner function : WE
Port : Subsystem
Outbput mode: Collect idoc
Basic type : Delvry01
Packet size: 1
Application: V2
Output type : LAVA
Process code: DELV.
You can post the delivery by selecting Logistics →Sales and Distribution →Shipping, Delivery
-->Create (transaction VL01). Output control is used to find the condition record and the shipping
notification is sent to the customer via EDI (IDoc Interface). The shipping time in the condition
record determines when the corresponding outbound IDoc is generated
On the Create Condition Records (Outg. ship notifica.): Fast Entry screen:
-->Enter customer number in Customer, SAP Ship-to # .
-->Enter WE in PartF.
-->Enter 6 in Medium.
-->Enter 4 in Time.
-->Enter EN in Language.
-->Choose Save.
thanks
mrutyun^

Value mapping in the ERP system during IDOC creation

We have a PI File-IDOC scenario.
We can translate simple mappings such as currency or unit of measure in PI(7.1) using the Value Mapping function. For complicated mappings involving business logic (e.g. Tax code which is derived from multiple fields) we want to perform these mapping in the ERP (ECC6) system. Is there an approved generic SAP standard process where these value mappings can be done in the IDOC creation which is still valid when re-processing?
e.g. a specific BADI or enhancement point recommended for these mapping?
There might also be a requirement to add segments based on value mapping logic for example when a tax record segment is only required for a non-zero tax code which is mapped via business logic.
Can someone please direct me in the right direction.

Thanks for your answers but I assumed that using a user exit / Enhancement point was obvious. What I'd like to know is a generic entry point that I can estabolish a IDOC enhancement framework. Somewhere I can call a class containing methods linked to IDOC message types
e.g. Call similar to my prototype (this will be where dependant on mappings certain segments will need to be inserted such as tax segments.
ASSIGN control-mestyp TO <mestyp>.
    CALL METHOD (<mestyp>)
      EXPORTING
        control        = control
        data           = data
      IMPORTING
        have_to_change = have_to_change
        protocol       = protocol
        new_entries    = new_entries.
The "entry point" must be processed both at creation and reprocess. We are also dealing with Inbound IDOCs not outbound

Change pointers to trigger the IDOC

HI
I am having a selection screen with fields to create a custom info record (transaction VD51/ VD52 )
Customer
material
salesorganisation
distribution channel
division
if we can use change pointers to determine when procedure is triggered.
Please provide the steps for that (including change document)or we need to check the CDHDR table using the following fields.
Plz suggest

Change pointers is the one of the IDOC processing method in ALE.
In this once we make the config to any of messages type , if any changes are made in sending system then IDOC will be posted directly to destination with user interation.
Changes pointers are configured using BD50,BD51,BD53,BD61.
Change pointers are stored in tables BDCP and BDCPS (or BDCP2 in case of high-performance setting) - like CDHDR and CDPOS for change documents (but this is not a controlling table!).
1. Do you really need change pointers?
You need change pointers to distribute changes with the ALE SMD tool. If you do not use this tool, you do not need to write change pointers.
You can deactivate change pointers and activate them again with the transaction BD61.
2. Do you really need to activate change pointers for this messages type?
If some messages types are no longer to be distributed by change pointers, you can
deactivate change pointers for this message type.
You can deactivate change pointers for the message type
and reactivate them again in transaction BD50.
For reduced message types, deactivate the change pointer with the
Reduction tool (transaction BD53).
Applications which write change documents will also try to write change pointers for ALE operations. These are log entries to remember all modified data records relevant for ALE.
Most applications write change documents. These are primarily log entries in the
tables CDHDR and CDPOS.
Change documents remember the modified fields made to the database by an
application. They also remember the user name and the time when the modification
took place.
The decision whether a field modification is relevant for a change document is
triggered by a flag of the modified fields data element. You can set the flag with
SE11 by modifying the data element.
For the purpose of distributing data via ALE to other systems, you may want to
choose other fields, which shall be regarded relevant for triggering a distribution.
Therefore R/3 introduced the concept of change pointers, which are nothing else
than a second log file specially designed for writing the change pointers which are
meant to trigger IDoc distribution via ALE.
So the change pointers will remember the key of the document every time when a
relevant field has changed.
Change pointers are then evaluated by an ABAP which calls the IDoc creation, for
every modified document found in the change pointers.
The Change pointers are written from the routine CHANGEDOCUMENT_CLOSE
when saving the generated change document. So change pointers are automatically
written when a relevant document changes.
The following function is called from within CHANGEDOCUMENT_CLOSE in order to write the change pointers.
CALL FUNCTION 'CHANGE_POINTERS_CREATE'
EXPORTING
change_document_header = cdhdr
TABLES
change_document_position = ins_cdpos.
Activation of change pointer update :
Change pointers are log entries to table BDCP which are written every time a transaction modifies certain fields. The change pointers are designed for ALE distribution and written by the function CHANGE_DOCUMENT_CLOSE.
Change pointers are written for use with ALE. There are ABAPs like RBDMIDOC
which can read the change pointers and trigger an IDoc for ALE distribution.
The change pointers are mainly the same as change documents. They however can
be set up differently, so fields which trigger change documents are not necessarily
the same that cause change pointers to be written.
In order to work with change pointers there are two steps to be performed
1) Turn on change pointer update generally
2) Decide which message types shall be included for change pointer update
R3 allows to activate or deactivate the change pointer update. For this purpose it
maintains a table TBDA1. The decision whether the change pointer update is active
is done with a Function Ale_Component_Check
This check does nothing else than to check, if this table has an entry or not. If there is an entry in TBDA1, the ALE change pointers are generally active. If this table is empty, change pointers are turned off for everybody and everything, regardless of the other settings.
The two points read like you had the choice between turning it on generally or
selectively. This is not the case: you always turn them on selectively. The switch to
turn on generally is meant to activate or deactivate the whole mechanism.
The change pointers which have not been processed yet, can be read with a function
module.
Call Function 'CHANGE_POINTERS_READ'
The ABAP RBDMIDOC will process all open change pointers and distribute the
matching IDocs.
When you want to send out an IDoc unconditionally every time a transaction
updates, you better use the workflow from the change documents.
Reward if useful

IDOCs creation - Transfer Orders(TOs) for Deliveries - Basic doubts, thanq

Hi Experts,
Am new to IDOCs. I hv a requirement, so, request u that, Can I get some Wht to do tips from u?
My doubts:
1- I hv been asked to create IDOC, Wht does it mean?
2 - How the created IDOC will be get posted?
My requirement is:
Original inbound idoc sent from Gentran will update the delivery with all serial numbers per material for all serialized product. The message code will be the indicator that a Transfer Order-TO, idoc must be created for TO confirmation.
I need to do===>   Should be executed only when the message code on the delivery idoc is u201CTOCu201D. Look up the warehouse code on the delivery header using the delivery nbr in the delivery idoc. Create a new TO confirm idoc per delivery idoc being processed. Create a line item on this idoc for every line on the delivery idoc. Each TO line includes the delivery number and delivery item number so the TO number and line number can be looked up in table LTAP by using the delivery number and line item number found on the delivery idoc. There will be at 2 transfer orders for each delivery item b/c of the 2 step pick process, so select the TO nbr that has 916 as the destination storage type (LTAP-NLTYP). There may be more than 1 pair of TOs per delivery item so this must be completed for each TO found relevant to each delivery item.
The inbound delvry03 idoc will update the delivery with the serial numbers as part of the standard functionality. Since the transfer order must also be confirmed with the quantities on the inbound idoc, an additional idoc must be created from within the delivery update process. The transfer order can be updated and confirmed using the standard idoc and function module which should be created and initiated from the delivery update function module customer exit.
Source = DELVRY03     Destination = WMTCID01
Record Name-Field Name-Record Name-Field Name-Description---Comments
E1EDL20     VBELN-E1LTCOH-LGNUM-Warehouse Number-Look w/ idoc delivery nbr
E1EDL20     VBELN-E1LTCOH-TANUM-Transfer Order Number- Look w/ idoc delivery nbr
E1EDL24     POSNR-E1LTCOI-TAPOS-Transfer Order Line Item- Look w/ idoc delivery line nbr
EVERY THING IS DATA TRIGGERED!!!
thanq
Edited by: Srinivas on Jun 27, 2008 4:41 PM

IDOC Programming
There are two processes in IDOC processing one is INBOUND PROCESS( IDOC coming to the system and its handling at various stages) and the other is OUTBOUND PROCESS( IDOC is send to other system . Separate ABAP programs are written for these 2 processes and different configuration settings are required for each one .Depending upon the trigeering mechanism different programming approaches are used.OUTBOUND PROGRAMS handle the IDOC creation and INBOUND PROGRAMS handle the inbound IDOC and the data trasfer from the IDOC to the database tables.
NEED FOR ABAP PROGRAMMING arises if
1)New IDOC was created
Depending upon the triggering mechanism i.e change pointer,message control
etc the programming technique changes and the type of process.
2)Existing IDOC was extended
User Exits are used to populate data in new segments added and to read them
back.
3)To enhance an exsiting process.
User Exits are used .
Basic structure of an OUTBOUND PROGRAM
The basic structure of all outbound programs is same. The CONTROL
record which is of TYPE EDIDC has to be filled. It contains important fields like
IDOCTP IDOC type
MESTYP Message Type
RCVPRN Recieving Partner (Destination)
RCVPRT Partner Type (it is LS i.e Logical System)
The DATA RECORD internal table which is of TYPE EDIDD has to be filled
in the same order as there are segments in the IDOC definition.
It has 2 important fields which are to be filled ,these are
SEGNAM Name of the segment
SEGDATA Data in the segment and can be upto 1000 bytes.This field
is corresponds to each data segment in the IDOC.
e.g.
DATA INT_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE.
DATA W_SEGDATA LIKE zsegment "custom segment zsegment
INT_EDIDD-SEGNAM = 'ZSEGMENT'
W_SEGDATA-field1 = value "taken from some table
W_SEGDATA-field2 = value "taken from some table
INT_EDIDD-SEGDATA = W_SEGDATA
APPEND INT_EDIDD
This will fill the data record corresponding to the segment ZSEGMENT . For all
segments the sam steps will be repeated until all the data corresponding to all the
segments in the idoc is filled in the internal table of type EDIDD.
There is only one control record and can be multile data records in the idoc
structure.
Which data is to be extracted from the tables to be filled in EDIDD type internal table is determined in standalone programs from the objects which are specified in the selection screen and from the object key passed to the function module in case of message control and is taken from BDCP table in case of change pointers using function modules "CHANGE_POINTERS_READ"
In case of stand alone programs and function modules based on change pointers method the function module "MASTER_IDOC_DISTRIBUTE" is used to send the IDOC to ALE layer for distribution ,in case of message control it is handled automatically by the RSNASTED program invoked by the message control.
OUTBOUND PROCESS AND OUTBOUND PROGRAM.
Outbound programs are used in outbound process to genearte IDOCs . There
purpose is to extract the data from the tables and to fill the IDOC data records
and the control record in the IDOC and pass ito the ALE layer for distribution to the recieving system .
Depending upon the triggering mechanism (how and when the outbound program will be started different techniques and interface is used for outbound program.
1)Message control
Application like PO(purchase order) creation use this technique , where the output type is linked to the application(Message control is a configurable cross application component which can be set in IMG .Such programs are created in the form of function modules and linked to the output type which is linked to the apllication.These have predefined interfaces.
In outbound programs(function module) that use message control the key of the
application document is passed to the function module whcig will read the data from the table depending upon the key passed(NAST structure) and fill the IDOC segemnts with the application data.The control record is also passed to the function module but is not fully filled, the rmaining fields are filled and the control is passed back to the calling program which is RSNASTED and is invoked by the
message control to process ALE and EDI output types and this program on recieving the IDOC data will create the physical IDOC in the system.
The parameteers passed to the function module are
IMPORTING PARAMETERS
OBJECT LIKE NAST
It contains documents key.
CONTROL_RECORD_IN LIKE EDIDC
It contains the partailly filled control record
EXPORETING PARAMETER
OBJECT_TYPE
CONTROL_RECORD_OUT LIKE EDIDC
TABLES
INT_EDID LIKE EDIDD
The internal table used to fill the data records in the same order as they exists in the IDOC.
The important parameters that should be filled in the custom function module are
CONTROL_RECORD_OUT and INT_EDIDD .The OBJK field of the structue NAST contains the key of the apllication document.
2)Stand alone programs
Generally used for Master Data transfer and as such depending upon the requirement can have different interfaces.The programs have a selection screen which has select options to select the objects, and parameters for specifying the recipient Logical System and the Message Type.
Data is selected based on the specified objects from the tables . and control record of type EDIDC is created and filled with important values like DIRECTION ,IDOCTP,RCVPRT,RCVPRN and MESTYP .
Data is filled in an internal table of TYPE EDIDD according to segment definitions
and in same order and the function module MASTER_IDOC_DISTRIBUTE is called passing the control record and the internal table containg IDOC data and importing an internal table consisting of control records for each communication IDOCS created.
3)Change pointer
Change Pointer table is read and checked if changes were made to important fields , if so the outbound program will be triggered automatically , these have predefined interfaces
ALE/IDOC Transaction
SALE Area Menu for ALE configurations.It includes transactions for
Logical System definition and linking it to a client, Transactions for
RFC Destination and Port Definition Etc.
SM59 RFC Destination
Here we specify the login settings for the destination including
the I.P address or Application Server name and the User name and
password.The information entered here is used to run Remote Function
Calls(RFC ) on the destination server .We can create number of types
of RFC Destinations but 3 types are important .
R/3 (R/3 to R/3), LS(logical system) and TCP/IP.
The name of the RFC destination should be same as that of Logical
System as it helps in creation of automatic partner profiles.
WE21 Port Definition.
There are 6 types of ports but only 2 types File and Transactional RFC
types of ports are important.
We have to specify the RFC Destination before a port can be created.
WE57 This is used to assign the Inbound function module to the Message Type
and to the IDOC Type.
WE42 This is used to define the process Code for Inbound Processing.
BD95 Define Filter object type .We can specify the field and the table it belongs
to as a filter object .
BD59 Assignment of Filter object type to the Message Type .Here we create the
link between Filter object and the segment and the message type and the
segment Field.
BD50 Set message Type to reducible.
BD65 Define Mandatory Fields.
BD64 Distribution Model . Also known as Customer Distribution Model Used to
define all the messages that will be exchanged between remote systems
and the name of thes logical systems. Any filters can also be specified.
The model once created has to be distributed on every system which will
be communicating ,It can be maintained on only One system.
BD21 Creating IDOcs from change pointers.
This can be used to create IDOCs from change pointers for a particular
message LIKE MATMAS.
BD22 This can be used to delete change pointers.
BD87 Status Monitor. Idocs can be selected base on number of criteria and there
processing status can be seen in detail.
BD10 Material Master Data Distribution .
Based on Message MATMAS.
BD12 Customer Master Data Distribution .
Based on Message CREMAS.
BD14 Vendor Master Data Distribution
Based on Message DEBMAS .
BDFG Generate ALE Interface for BAPI.
Here we specify the Business Object and the BAPI Function module for
which the interface has to be created.
WE31 Segment Editor.
This is used to create segments. We create the segment type and
segment definition is automatically created by editor e.g. Z1DUMMY is
segment type and Z2DUMMY is the segment definition .We specify the
fields and the data elements these cp\orresponds to create segments.
WE30 IDOC Editor
It is used to create a new IDOC Type or IDOC Extension .We specify the
segments that will be addd to the IDOC type.
WE02/05 IDOC List.
Various selct options and parameters are provided to select IDOCs
depending on the date, direction , mesage type etc.
WE20 Partner Profile
Here we create partner profile for each and every partner from / to which
the messages will be exchanged.There are 6 types of PF generally only
profiles of type LS(Logical System) ,KU(Customer) ,LI(Vendor) is used.
We specify the partner number and partner type and the agent and
the agent type responsible for handling of errors .
For every message send to the partner we have a outbound record and for
evry message coming from the partner we have the inbound record .
We specify the message in the otbound/inbound records ,double
clicking will take us to the detailed screen where the IDOC Type ,Port
and whether the IDCO will be immediatelt processed or collected are
mentioned.

Where is the IDOC Sender field set?

I have been asked to help solve an IDOC problem wherein a system is sending IDOCS with different values for the control record sender field. I am a BASIS person, so I know quite a bit about the IDOC transmission process but not much about the creation of them.
The IDOCS cover the basic buy/sell scenarios:
purchasing: ORDERS, ORDRSP, DESADV, INVOIC
sales: ditto, but in the opposite direction.\
The complaint is that for a given business partner, different IDOC types have different sender IDs. So the partners get DESADVs from sender BLERK and INVOICs from sender GURGLE. The actual sender values used are not related to the client's Logical System name (for example, one of them is '0101' which indicates that a customizing person might have put junk data into a field they did not understand.)
I am trying to figure out how the sender is being set. AFAIK there are no user exits and no IDOC rules in place.
IDOCs are sent from the ABAP system through a Business Connector, so I am interpreting the "Process Integration" topic of this forum in the broader sense, but I could not find a more appropriate forum.
There are various options for me to overwrite the sender - for example I can stomp it in the business connector, but I would rather fix the problem at the source and educate the monkeys that cause the problem in the process.
I have not been able to find anything in the partner profiles and output condition records for this.
Please tell me where the SENDER value can be set for any of the outbound logistics IDOCS.
Thanks,
Russ.

Hi Russell,
as you mentioned IDOC are getting triggered from ABAP.. that means,,
is your IDOC is Inbound IDOC or Outbound IDOC..?
if it is your Inbound IDOC then check for following details.
this is the problem of Partner profile.
check from which system you are getting this IDOC triggered.. if it is PI then check for related interface in PI and in interface you will be able to get this information that from where you are getting this Sender value how you are getting..and you can then change it accordingly in PI if PI is sending you that IDOC..
this is not necessary that IDOC will triggered from PI only as ABAP program can also triggered and create IDOC.. so in that case check which program or function module is generating that IDOC .. then in that you will get information before generating what values are getting passed to these control record.. so you can change it there...also..
if the IDOC is Outbound IDOC:
then in this your ABAP program is generating that IDOC and check for program or function from where this IDOC is getting generated and change the logic to fill control records ..
Thanks,
Bhupesh

How long should the Repository Creation Utility take for Oracle Portal?

I'm running the Oracle Repository Creation Utility (RCU) as a precursor to installing WebCenter, and the schema creation process is stuck on the "Portal" step. The first 10-12 steps each took less than 30 seconds to complete, and the last step has been going for 2 hours 14 minutes.
I checked the rcu log files, and they are constantly being updated with new progress information as though the process is still working. I haven't been able to find anyone else on the internet with this problem. From various screenshots on google, it looks like it can complete in under 10 minutes in some cases.
Thanks,
Dave

Is it showing some error ?
Check with DB settings and parameters properly.Usaully it should not take long time to complete.Possible chances are corrupt rcu file.I would suggest download again the RCU and re-run it.
Anyways in which version of DB you are trying to install ?(vendor and version).
Which version of RCU you are using ?
Regards,
Hoque

Database creation process hangs

I am manually creating a database on Windows 2k3 server using Oracle 11 r2. Using the Database Configuration Assistant to create a database, the process hangs for hours.
I figured out and triedthe following:
1. I have attempted using the GUI tool more than once to create the database and each time it hangs.
2. Using the scripts have been created using the with configuration tool, I manually attemped to create database. -- I have attempted more than once.
3. The database creation process hangs while running the EXECRM.SQL file that is called by the CATPCNFG.SQL which is called by CATPROC.SQL which is called by CreateDBCatalog.sql
3. The EXECRM.SQL file hangs on the following statement EXECUTE DMBS_RMIN.INSTALL;
I'm not sure why the PL/SQL packag is hanging at this point. Any help is appreciated.
Thanks,
Sheila

I was able to create the databases prior to installing Enterprise Manager Grid control. I deleted the databases to re-create so they would be registered with Enterprise manager. Once I install Enterprise manager the creation process hung. I have also installed Essbase and Oracle/Hyperion Enterprise Performance Management Suite on the server. I'm trying to do some research on these BI tools.
I'm tempted to uninstall Essbase and the Hyperion producst along with Enteprise Manager and start from scratch to test to see if I can create a database without these other products.

IDOC Inboun processing success but no record posted to table

Hi,
We are performing ALE refresh in RCD221 (development system). The ALE IDOCS are extracted for HR area with Message class as HRMD_A, the IDOCS are processed successfully from the sending system (RCB) and reaches the receving system RCD221. While we process the inbound IDOCS in RCD221 records are not getting posted in the table, however the IDOC status is shown as successful (53). This is happening when we are processing the data for object type 'P'.
Regards,
Bharath Mohan B.

RFC destinations, Logical systems, and then Partner profiles needs to be maintained. and You need to create the Distribution model in sender system.
Partner profiles maintained in both the systems, soure Outbound properties
Target Inbound properties.
if you have two clients in system it will be easily you can check.

Idocs not processed automatically in BW

Dear Experts,
I have a scenario here where I extract data from source system via process chains.
The source system job completed and in BW, the outbound idocs resulted in the following Status (02).
02 Error passing data to port 1
In the infopackage message dialog, I got the message as
Could not find code page for receiving system
Errors have been reported in Business Information Warehouse during the IDoc update:
In order to resolve this, I'm manually processing the idoc using program RBDAGAIN.
Note: This issue occurs only when I trigger the infopackage via process chains.
How do I rectify this error so that the idocs are processed automatically in BW?
Br, Harish

Hi,
how much time your ecc job takes to finish job.
Is this process chain newly created one or old one?
if its old one, any changes were applied on this process chain recently?
is it showing any idoc numbers at below status bar.
if yes then try to pull them by using t code BD87.
Can you share info pack error message screen shot.
Thanks

Idoc trfc processing very slow

Hello,
I am troubleshooting slow processing of idocs in an Xi test system.
idocs are being processed at a rate of betwen 40 / 60 per hour so at the current rate there will stil be another 3 days (approx) until the queue is cleared.
In SMQS on the Xi (source) system the specific idoc destination is set-up as follows: -
Clt - 10
Destination - R2RREG100
Type - R
W/o tRFC -
Max.Conn. - 10
Max. Runtime - 60
Status - WAITING
Act.Conn - 5
Host ID - ax2t003a_X2T_43
The RFC connection between the two systems has been tested successfully.
Selecting TRFC Monitor and there are still over 3000 rows similar to the following (was over 7000 when first checked)
Caller - PIAFUSER
Function Module - IDOC_INBOUND_ASYNCHRONOUS
Target System - R2RREG100
Date - 15.12.2011
Time - 12:38:22
Status Text - Transaction recorded
Transaction ID - 8218046C00014EC9DE911C9B
Host - ax2t003a
Tctn
Program - SAPMSSY1
Cln - 10
Rpts - 30
I am told by the application team that processing 7000+ idocs is not a large amount for this system
The Xi (source) system and the R3 destination system have both been restarted to clear memory etc but this has not improved speed of processing.
I presume the problem was caused by trying to process too many idocs at once through the Xi system as mentioned in SAP Note 1548446.
I have read SAP Note 1483757 and checked ST03n last minute load on RFC table in the R3 destination system -
Task Type Name - RFC
#Sequential Read - 4,782,264
T Seq Read - 1,157
Avg Seq Read - 0.2
#Accesses -      13,515,579
T Time - 204
Avg T - 0.0
#Changes - 54,206
T Changes - 63
Avg Changes - 1.2
Calls - 18,352,049
Avg Time - 0.1
#Reads - 1,828,651
#DB Recs- 109,376
#Records - 7,687,467
#Calls - 0
T Time - 0.0
Avg Time - 0.0
Last minute load Table Statistics for the destination system ARFCRSTATE table shows the following :
Table Name - ARFCRSTATE
Records -      1,822
Modifiable - 226
records - 0
Sequential Reads - 1,596
T Access - 1
In accordance with the note I tried setting the following on the detaination system but did not see any improvement in processing speed so have now removed the parameter and scheduling of the report.
    1. Set the profile parameter abap/arfcrstate_col_delete to 'X' on the default profile of the destination system.
    2. Periodically schedule the RSTRFCEU batch job in intervals of 5 minutes, in the destination system.
Q1 -after setting 'abap/arfcrstate_col_delete' I did not restart the R3 system. Is a restart required for this to take effect?
Q2 - What else should I check to identify why idocs are being processed so slowly ?
Q3 - Is there anything else I could change to speed up processing ?
Many thanks,

Many thanks jbagga for your reply.
My issue was resolved by SAP who suggested changing the processing mode for message type in WE20 on the receiver system from "Trigger Immediately" to "Trigger by background program".
With the processing mode set to "Trigger Immedaitely" the sender system calls the receiver, the idoc is stored on the dateabase and the application processing was carried out in the same LUW. As a result of this the send must wait until the application finishes processing the messages before it can anything else.
The processing mode was changed to "Trigger by background program" which decoupled the IDoc transfer from the IDoc application processing, performance immediately improved in the XI (sender) system and cleared the queue.
Regards,

Activating the IDOC Creation Process

Similar Messages

Maybe you are looking for