Logiacal path deactivate in IDOC

Dear Sir,
We are doing the hardware migration project.
hence we have installed new SAP system in new H/W and completed the data migration from production system.
Now we are in the testing phase, so we would like to disable the entry temporarily in
Idoc new SAP system(Trns: File) to avoid the disturbance of production system.
We want to use the same logical path again for multiple testing
Could someone tell me how to inactive(Prodcution server IP address logical path) temporarily the entry in File transaction. ?
Thanks
Elumalai

I would just put a fake entry in your hosts file like
127.0.0.2 <hostname-of-production-system>
Since 127.* are lookback addresses the system will try to connect to itself (and fail) and hence your production will not be impacted.
Markus

Similar Messages

How to Configure logical path and how to retrieve physical path for an IDOC

Hi ,
I want to configure logical path for an IDOC,
and then I need to retrieve Physical path from this logical path
using a FM (eg. FILE_GET_NAME).
How to configure the logical path for an idoc ?
Regards ,
Harshit Rungta

Using Logical Files in ABAP Programs
To create a physical file name from a logical file name in your ABAP programs, use the function module FILE_GET_NAME. To insert the function module call in your program, choose Edit ® Insert statement from the ABAP Editor screen. A dialog box appears. Select Call Function and enter FILE_GET_NAME. The parameters of this function module are listed below.
Import parameters
Parameters
Function
CLIENT
The maintenance tables for the logical files and paths are client-dependent. Therefore, the desired client can be imported. The current client is stored in the system field SY-MANDT.
LOGICAL_FILENAME
Enter the logical file name in upper case letters that you want to convert.
OPERATING_SYSTEM
You can import any operating system that is contained in the list in Transaction SF04 (see Assigning Operating Systems to Syntax Groups). The physical file name will be created according to the syntax group to which the operating system is linked. The default parameter is the value of the system field
SY-OPSYS.
PARAMETER_1
PARAMETER_2
If you specify these import parameters, the reserved words in the physical path names will be replaced by the imported values.
USE_PRESENTATION
_SERVER
With this flag you can decide whether to import the operating system of the presentation server instead of the operating system imported by the parameter OPERATING_SYSTEM.
WITH_FILE_EXTENSION
If you set this flag unequal to SPACE, the file format defined for the logical file name is appended to the physical file name.
Export Parameters
Parameters
Function
EMERGENCY_FLAG
If this parameter is unequal to SPACE, no physical name is defined in the logical path. An emergency physical name was created from table FILENAME and profile parameter DIR_GLOBAL.
FILE_FORMAT
This parameter is the file format defined for the logical file name. You can use this parameter, for example, to decide in which mode the file should be opened.
FILE_NAME
This parameter is the physical file name that you can use with the ABAP statements for working with files.
Exception Parameters
Parameters
Function
FILE_NOT_FOUND
This exception is raised if the logical file is not defined.
OTHERS
This exception is raised if other errors occur.
Suppose the logical file MYTEMP and the logical path TMP_SUB are defined as in the preceding topics and we have the following program:
DATA: FLAG,
      FORMAT(3),
      FNAME(60).
WRITE SY-OPSYS.
CALL FUNCTION 'FILE_GET_NAME'
     EXPORTING
          LOGICAL_FILENAME        = 'MYTEMP'
          OPERATING_SYSTEM        = SY-OPSYS
          PARAMETER_1             = '01'
     IMPORTING
          EMERGENCY_FLAG          = FLAG
          FILE_FORMAT             = FORMAT
          FILE_NAME               = FNAME
     EXCEPTIONS
          FILE_NOT_FOUND          = 1
          OTHERS                  = 2.
IF SY-SUBRC = 0.
WRITE: / 'Flag      :', FLAG,
         / 'Format    :', FORMAT,
         / 'Phys. Name:', FNAME.
ENDIF.
The output appears as follows:
HP-UX
FLAG :
FORMAT : BIN
Phys. Name: /tmp/TEST01
In this example, the R/3 System is running under the operating system HP-UX, which is member of the syntax group UNIX. The logical file name MYTEMP with the logical path TMP_SUB is converted into a physical file name /tmp/TEST01 as defined for the syntax group UNIX. The field FNAME can be used in the further flow of the program to work with file TEST01 in directory /tmp.
Suppose we have a logical file name EMPTY with the physical file name TEST, connected to a logical path that has no specification of a physical path. If you replace the EXPORTING parameter 'MYTEMP' with 'EMPTY' in the above example, the output appears as follows:
HP-UX
FLAG : X
FORMAT :
Phys. Name: /usr/sap/S11/SYS/global/TEST
The system created an emergency file name, whose path depends on the installation of the current R/3 System.

How do we find out the file path which the IDOC is stored.

Hi,
If we use T-code: AL11, we can see the file path of the Unix server. And some IDOC outbound file is also stored in some file path after generated.
If i generated an outbound IDOC, how do i know in which file path it stored??
Thanks

Hi,
Go to control record of the outbound IDOC.
go to partner tab, check the port under sender information.
the outbound file path will be configured with your port.
Use T-code WE21, the concerned port will be available under section 'File'
Directory under tab Outbound file will show the path under which file has been stored.

Process flow of IDoc adapter in SAP PI

Hi Experts,
can any one pls send me about IDoc adapter in SAP PI/XI, which covers a complete info of IDoc adapter.
i mean complete in and out about IDoc adapter.
with rgds,
MF

Hi
If you do a search, you will get lots of material.
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b2b4035c-0d01-0010-31b5-c470d3236afd
IDOC Adapter
https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/idoc%252badapter
These links should help you out
Thanks
Saiyog

Ale Idoc

I am sending an idoc from one system to another system, in the receiving system idocs status is 64.
its not posted.
In WE20 partner profiles, I have assigned a process code to the message type CHRMAS(characteristic master) in inbound parameters for
the corresponding logical system
Again I have assigned that procees code to FM "IDOC_INPUT_CHRMAS" with option as "processing with ALE" and type as "processing by function module".
I have checked "Trigger by background program" for processing by fun module.
When i tried to push the idoc thro BD87, it works successfully.
Could anybody help in this, what other check should i need to do so that idoc posts automatically.
Thanks in advance,
Ponraj.s.

Hi,
For the path of Scheduling Idoc processing inreceiver system :
Go to transaction SALE ->Modeling and Implementing Business Processes -> Partner Profiles and Time of Processing -> Scheduling IDoc Processing in Receiving System.
Define Variant & schedule a job.
Thanks.
Mark points if helpful.

PI 7.4 - interface from ECC(idoc) JDBC, idoc not making it from sm58 '

Hi Experts,
I've got an interface which works in our dev and 2 of our test systems but NOT the 3rd test system. It doesnt work in our live system either. (essentially its a split receiver determination - goes to both jdbc and a file).
I've reintroduced the config from the dev system to the 3rd test system and overwritten its ico/scenario in the hope that it might work - it didnt make any difference as was getting the first error below in bold.
I've checked all RFC connections, destinations, partner profiles and ports, all seem in order and mirror systems that work, bar the naming conventions.
I've checked The FM version, its the same version as the system which works.
In sm58 I was originally getting the error 'Commit fault: ASJ.ejb.005043 (Failed in component:sap.com/com.sap.aii.ad', upon 'googling' this error it was suggested on SCN to essentially delete old config and reimport / rebuild the interface (Commit fault: ASJ.ejb.005043) . I've tried to reimport the config scenario / ico, i then deleted the config scenario and reimported it. This hasnt worked.
I have had our Basis team double check the NWA settings, and the ResourceAdaptor settings were reset.
When re running the trfc in sm58, i now get the error ' Failed to resolve repository reference @XI_IDOC_DE FAULT_DESTINATION_DEV'
Would appreciate some feedback as to what to try next..

Hi George,
We have seen this issue sporadically too while deploying to our QA system. What I have generally done in the past to get it working is the following (I have run all the steps because I don't know if they are all required to get it going again):
1. Open ID and clear the SLD data cache
2. Open sender system in ID and do compare of adapter specific identifiers with SLD and then apply
3. Deactivate sender IDoc channel and then reactivate (I would double check your destination in the settings also)
Hopefully this will help.
Regards,
Ryan Crosby

How to define interface of IDOC?

IDoc outbound:
In step 1, a new file is generated with the transferred IDocs by the IDoc Interface. In the second step,
the program ¡°rfcexec¡± (synchronous RFC) with the path to an executable program is called (here:
¡°out.script¡±) and also the path to the IDoc file. ¡°out.script¡± thus contains the path and name of the
file as an input value. In step 3, it therefore calls the external system, which reads the file in step 4.
After successful processing of the IDoc file, the external system must delete the IDoc file. The call
command in ¡°out.script¡± depends on the external system.
I quated this from relative document,I want to know how to define 'rfcexec' and 'out.script' looking forward to ur reply,
best regards

Hi Aparajitha,
Master_idoc_distribute for sending outbound IDOCs.
Thanks,
Anil

Output type for movement type for IDOC creation

Dear Experts,
Can anybody tell how to create "Output type for different movement types for IDOC creation"
Specially for Movement type used for Inbound & outbound.

Hi,
pls find below link's
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/abap/idoc%2bsteps
BAPI & IDOC material
IDOC Scenario Steps
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://sap.niraj.tripod.com/id51.html
http://www.thespot4sap.com/Articles/SAP_ALE_IDOCS.asp
Changing fields in an Idoc segment
Regards
Raj.

Materials for idoc

Hi am interested to learn about idocs can you provide me some useful links

Hi saranya srithar ,
IDoc is an Intermediate document that holds application data.
A container used to exchange data
It is independent of the complex SAP structure to store data.
It serves as the vehicle for data transfer.
IDoc Type defines the structure and format in which the data is exchanged.
It is similar to a structure in SAP
IDoc data is an instance of IDoc Type
IDoc acts as a standard SAP interface to exchange business data through ALE.
From an SAP system, an IDoc can be sent to and received from
An SAP R/3 system
An SAP R/2 system
An EDI subsystem
Any third-party application software
Segments . Idoc data is arranged in Rows, The rows make up segments of an idoc. Each segment consists of fields/segments. Fields can contain data.
These r all the t/codes which we will come across in IDocs:
TCODE     TTEXT
BD10     Send Material
BD100     IDoc display object channel view
BD101     Consistency check
BD102     Outbound registry
BD103     Inbound registry
BD104     maintain tbd53
BD105     Maintain Supported Business Objects
BD11     Get Material
BD12     Send customer
BD13     Get customer
BD14     Send vendor
BD15     Open vendor
BD16     Send Cost Center
BD17     Get Cost Center
BD18     Send General Ledger Account
BD19     Get General Ledger Account
BD20     IDoc passed to application
BD21     Select change pointer
BD22     Delete change pointers
BD23     Delete serialization data
BD24     Send Cost Elements
BD25     Send Activity Type
BD26     Get Activity Type
BD27     Send cost center activity prices
BD28     Send obj/cost element control data
BD30     Distribute material object list
BD31     Distribute document object list
BD32     Distribute plant allocations(matBOM)
BD33     Distribute material variants (ALE)
BD34     Distribute order BOM
BD35     Send Business Process Groups
BD36     Send Business Processes
BD37     Send Business Process Price
BD40     Read change pointer for group
BD41     Dispatch IDocs for group
BD42     Check IDocs for group
BD43     Post IDocs for group
BD44     Assign Message Types to Serlz. Group
BD47     Dependencies between methods
BD48     Dependency method - message
BD50     Activate Change Ptrs for Mess. Type
BD51     Maintain function modules (inbound)
BD52     Activ.change pointer per chng.doc.it
BD53     Reduction of Message Types
BD54     Maintaining Logical Systems
BD55     Maintain IDoc Conversion
BD55OLD     Maintain IDoc Conversion
BD56     Maintain IDoc Segment Filters
BD57     Maintain link and serialization ty.
BD58     Convert organizational units
BD59     Allocation object type -> IDoc type
BD60     Additional data for message type
BD61     Activate Change Pointers - Generally
BD62     Define Segment Conversion Rule
BD62OLD     Define Segment Conversion Rule
BD63     Transport ALE Tables of Message Type
BD64     Maintenance of Distribution Model
BD65     Maintain IDoc type required fields
BD66     IDoc type field -> change doc.field
BD67     Maintain methods (inbound)
BD68     Maintain Lists
BD68OLD     Maintain Lists
BD69     Assignment of Message Type to IDoc
BD70     Synchronize Number Ranges
BD71     Define FM for dependent bus. object
BD72     Activate Events
BD73     Reposting of IDocs (ALE)
BD75     Convert IDoc Status
BD77     Distribution of control data
BD78     Monitoring control data distribution
BD79     Maintain IDoc Conversion Rules
BD79OLD     Maintain IDoc Conversion Rules
BD81     Filter objects parameter filtering
BD82     Generate Partner Profiles
BD83     Send IDocs after an ALE error
BD84     Post IDocs after ALE error
BD85     Consistency check for transfer
BD86     Consistency check for sales
BD87     Status Monitor for ALE Messages
BD89     Control data model. - initial screen
BD91     Send Characteristic
BD92     Send Class
BD93     Send Classification
BD95     Specify ALE object types
BD96     filter objects of receiver determin.
BD97     Assign RFC dest. to Logical Systems
BD98     Consistency Check Workflow Connectn.
BD99     Message type dependencies
WE02     Display IDoc
WE05     IDoc Lists
WE06     Active IDoc monitoring
WE07     IDoc statistics
WE08     Status File Interface
WE09     Search for IDocs by Content
WE10     Search for IDoc in Archive
WE11     Delete IDocs
WE12     Test Modified Inbound File
WE14     Test Outbound Processing
WE15     Test Outbound Processing from MC
WE16     Test Inbound File
WE17     Test Status File
WE18     Generate Status File
WE19     Test tool
WE20     Partner Profiles
WE21     Port definition
WE23     Verification of IDoc processing
WE24     DefaultValuesForOutboundParameters
WE27     DefaultValues for Inbound Parameters
WE30     IDoc Type Development
WE31     Development IDoc Segment
WE32     Development IDoc View
WE34     Object for Display of XML IDocs
WE40     IDoc Administration
WE41     Process codes, outbound
WE42     Process codes, inbound
WE43     Funct.module: Status record display
WE44     Partner Types and Checks
WE45     Forward (inbound) (V3, EDILOGADR)
WE46     Error and Status Processing
WE47     Status Maintenance
WE50     System process codes: Texts
WE51     System process codes: Change texts
WE54     FMs for changing file names
WE55     Function Module for Path Names
WE56     IDoc Administration
WE57     Assignment Messages for Appl. Objs
WE58     Status process codes: Texts
WE59     Change status process codes
WE60     Documentation for IDoc types
WE61     Documentation for IDoc record types
WE62     Documentation for segments
WE63     Documentation
WE64     Documentation message types
WE70     Conversion: Basic types
WE71     Conversion: Extensions
WE72     Conversion: IDoc types
WE73     Conversion: Logical messages
WE81     Logical message types
WE82     Assign Messages for IDoc Type
WE84     Assignment of IDoc and appl. fields
WE85     Create Rule Names
WEBU     Printing Labels via Assortment List
WEDI     EDI Basis
WEINBQUEUE     IDoc Inbound Queue
WEKF     Purchase order SAP Retail
WEL0     Forward (inbound) (EDILOGADR)
WEL1     EDI: Interface Invoice for EDILOGADR
WELI     Maintain Status Groups
cheers!
gyanaraj

What is necessary for MM in IDOC and ALE??

hii
What is ALE, EDI and IDOC in SAP??
Explain the above things with example
What i have to learn as MM consultant to work on support project ..
Can some body explain me with their real time experience
Thanks

HI,
Difference Between EDI and IDOC
EDI is nothing but Electronic data interchange. SAP will support EDI through Intermediate documents (IDOCS).
EDI (Electronic Document interchange) - EDI is the electronic exchange of business documents between the computer systems of business partners, using a standard format over a communication network.
EDI is also called paperless exchange.
Advantages:
Reduced Data entry errors
Reduced processing time
Availabilty of data in electonic form
Reduced paperwork
Reduced Cost
Reduced inventories and better planning
Standard means of communications
Better business process
EDI has two process
1. Outbound process
2. Inbound process
OP:
1.Application document is created.
2.IDOC is generated
3.IDoc is transferred from SAP to Operating system layer
4.Idoc is converted into EDI standards
5.Edi document is transmitted to the business partner
6.The Edi Subsystem report status to SAP
IP:
1.EDI transmission received
2.EDI document is converted into an IDOC
3.IDOC is transferred to the SAP layer
4.The application document is created
5.The application document can be viewed.
IDOC:
IDOC is a container that can be used to exchange data between any two process.
Each iDoc is assigned a unique number for tracking and future reference.
iDoc Consist of several segments,and segments contain several fields.
iDoc contains the following three type of records...
1.One Control Record.
2.One or many Data Record
3.One or many Status record.
PORT:
Port is used in the outbound process to determine the name of the EDI subsystem program,the directory path where the idoc file will be created at the operating system level,the idoc file names and the rfc desinations.
RFC Destination:
Used to define the characteristics of communication links to a remote system on which a functions needs to be executed.
Partner Profile:
Partner profile specified the various componets used in an outbound process ( Partner number,IDoc type,message type,Port,Process code),the mode in which it communicates with the subsystem(batch or immediate) and the person to be notified in case of errors.
Message Control
Used in pricing,account determination,material determination,and output determination.The message control component enables you to encapsulate business rules with out having to write abap programs.
Process:
Setup RFC destinations SM59
Port Destinations WE21
Partner Profile WE20
Message control NACE
Purchase Order ME21
Check IDOCs WE02,WE05
Explain to me about Idoc?
IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system.
IDocs are used for asynchronous transactions: Each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database.
Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.
A large enterprise's networked computing environment is likely to connect many geographically distributed computers to the main database. These computers are likely to use different hardware and/or operating system platforms. An IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another.
IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands.
An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication
layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model.
The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system.

Urgent Plz:Idoc errors

In some idocs if the idocs are not posted there would be multiple error message for the particular idoc.Where can we view the multiple error messages?

Hi Hema,
Go to tcode : We09 for status for the IDOC.
Transaction Code         Short text
WE02                     Display IDoc
WE05                     IDoc Lists
WE06                     Active IDoc monitoring
WE07                     IDoc statistics
WE08                     Status File Interface
WE09                     Search for IDoc in Database
WE10                     Search for IDoc in Archive
WE11                     Delete IDocs
WE12                     Test Modified Inbound File
WE14                     Test Outbound Processing
WE15                     Test Outbound Processing from MC
WE16                     Test Inbound File
WE17                     Test Status File
WE18                     Generate Status File
WE19                     Test tool
WE20                     Partner Profiles
WE21                     Port definition
WE23                     Verification of IDoc processing
WE24                     DefaultValuesForOutboundParameters
WE27                     DefaultValues for Inbound Parameters
WE30                     Development IDoc Type
WE31                     Development IDoc Segment
WE32                     Development IDoc View
WE34                     Object for Display of XML IDocs
WE40                     IDoc Administration
WE41                     Process codes, outbound
WE42                   Process codes, inbound
WE43                   Funct.module: Status record display
WE44                   Partner Types and Checks
WE45                   Forward (inbound) (V3, EDILOGADR)
WE46                   IDoc administration
WE47                   Status Maintenance
WE50                   System process codes: Texts
WE51                   System process codes: Change texts
WE54                   FMs for changing file names
WE55                   Function Module for Path Names
WE56                   IDoc Administration
WE57                   Assignment Messages for Appl. Objs
WE58                   Status process codes: Texts
WE59                   Change status process codes
WE60                   Documentation for IDoc types
WE61                   Documentation for IDoc record types
WE62                   Documentation for segments
WE63                   Documentation
Transaction Code         Short text
WE64                   Documentation message types
WE70                   Conversion: Basic types
WE71                   Conversion: Extensions
WE72                   Conversion: IDoc types
WE73                   Conversion: Logical messages
WE81                   Logical message types
WE82                   Assignment Messages for IDoc Type
BD87 u check the status monitoring for IDOC
cheers
Mohinder Singh Chauhan

Evalution path for PFAL to handle concurrent employee asignment.

Hello,
While using PFAL to push any object of type 'P'(employee), the standard process is creating IDoc segments only for the given employee, But how is it possible to create IDoc segments for its other assignments also?
I need to create IDoc segments of all the assignments for the employee given in PFAL selection screen.
Is there any evalution path (relating to 'CP') could help?
Thanks.
Edited by: Parthasarathi Mohanty on Jun 1, 2011 1:01 PM

Hi,
Thanks,
A209 evaluation path adds the IDoc segment of the Central Person (CP) related to the 'P'.
I need the IDoc segments of all the assignments of the P.
For e.g: The 'P' entered in the selection screen of PFAL has 3 assignments with a single CP.
I need the IDoc segments to be created for all the 3 assignments. (Segments related to CP not required)

Program to compare Idocs

Hi Experts,
Does anyone know a program/ transaction to compare two IDOC's of same Idoc type.
Please help.
Regards,
Kiran

Hi Kiran,
Check this link..
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/snippets/idoc%2bdiff%2b-%2breport%2bto%2bcompare%2bidoc%2bmessages
this might be useful.
i don't think there is any standard transaction for this.
check tcode WE60 or area menu tcode WEDI for all IDOC related transactions
Sachin

Main Difference Between EDI and IDOC Based On RFC

In IDOC ,RFC is Used to define the characteristics of communication links to a remote system on which a functions needs to be executed.
What About EDI ?

Hi Saurabh,
Check this..Hope it helps you.
EDI is nothing but Electronic data interchange. SAP will support EDI through Intermediate documents (IDOCS).
EDI (Electronic Document interchange) - EDI is the electronic exchange of business documents between the computer systems of business partners, using a standard format over a communication network.
EDI is also called paperless exchange.
Advantages:
Reduced Data entry errors
Reduced processing time
Availabilty of data in electonic form
Reduced paperwork
Reduced Cost
Reduced inventories and better planning
Standard means of communications
Better business process
EDI has two process
1. Outbound process
2. Inbound process
OP:
1.Application document is created.
2.IDOC is generated
3.IDoc is transferred from SAP to Operating system layer
4.Idoc is converted into EDI standards
5.Edi document is transmitted to the business partner
6.The Edi Subsystem report status to SAP
IP:
1.EDI transmission received
2.EDI document is converted into an IDOC
3.IDOC is transferred to the SAP layer
4.The application document is created
5.The application document can be viewed.
IDOC:
IDOC is a container that can be used to exchange data between any two process.
Each iDoc is assigned a unique number for tracking and future reference.
iDoc Consist of several segments,and segments contain several fields.
iDoc contains the following three type of records...
1.One Control Record.
2.One or many Data Record
3.One or many Status record.
PORT:
Port is used in the outbound process to determine the name of the EDI subsystem program,the directory path where the idoc file will be created at the operating system level,the idoc file names and the rfc desinations.
RFC Destination:
Used to define the characteristics of communication links to a remote system on which a functions needs to be executed.
Partner Profile:
Partner profile specified the various componets used in an outbound process ( Partner number,IDoc type,message type,Port,Process code),the mode in which it communicates with the subsystem(batch or immediate) and the person to be notified in case of errors.
Message Control
Used in pricing,account determination,material determination,and output determination.The message control component enables you to encapsulate business rules with out having to write abap programs.
Process:
Setup RFC destinations SM59
Port Destinations WE21
Partner Profile WE20
Message control NACE
Purchase Order ME21
Check IDOCs WE02,WE05
Explain to me about Idoc?
IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system.
IDocs are used for asynchronous transactions: Each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database.
Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.
A large enterprise's networked computing environment is likely to connect many geographically distributed computers to the main database. These computers are likely to use different hardware and/or operating system platforms. An IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another.
IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands.
An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication
layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model.
The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system.
Re,Manas

SWU3 - Automatic workflow customizing

Hi All,
We have a situation where all users are receiving error messages in their SBWP inbox. most of them are related to error processing with IDoc. the user inboxes are flooded with error message and they are not able to open their SBWP.
It seems that in SWU3 - automatic workflow customizing setting "Idoc interface" is active.
Path : SWU3 > "Classify Task as General" > IDoc Interface (checked).
We need to deactivate this Idoc interface but we are not able to do the same. Can some one let us know how to do this.
Also if there is some other cause of this problem then please let us know. Currently we are purging the error workitems but they keep on generating in the background.
Please help.
Regards,
Rohit

Hi,
We need to deactivate this Idoc interface but we are not able to do the same. Can some one let us know how to do this.
For this purpose you need to contact BASIS team to deactivate this.
Alternate solution :
Get the task id of that workitem. Open it through tcode PFTC and make the task attribute form to "General Task" to "Forwarding not allowed".
Run PFCT
Enter tour Task id ( eg. TS00008068 , please remove leading TS )
Addition data >>> Agent assignment >>> Maintain >>> Attributes
Form the next run of the workflow workitem will not reach to SBWP.
For the workitems you need to delete mannualy or forward it to a idle user.
Thanks and regards,
SNJY

Logiacal path deactivate in IDOC

Similar Messages

Maybe you are looking for