Lookup is possible for IDOC?

Hi All,
I am in the need of help in the lookups.
Here is my situation:
I want to get a data from the SAP tables and do some logic in the mapping and need to use the message mapping.
I am using the IDOC for my target end. I read some of the blogs and with my understanding we can use DB lookup, RFC lookup and SOAP lookup.
What about is we use IDOC? Is it possible to use in IDoc?
If it is possible can you guide me.
Thanks,
Jane.

Hi,
As Expert Raj mentioned
> DB system then u need to do JDBC lookup. If the data is available in R/3 then u've to do RFC lookup.
The following Blog might help you
/people/siva.maranani/blog/2005/08/23/lookup146s-in-xi-made-simpler
/people/sravya.talanki2/blog/2005/12/21/use-this-crazy-piece-for-any-rfc-mapping-lookups
/people/alessandro.guarneri/blog/2006/03/27/sap-xi-lookup-api-the-killer
Regards
Agasthuri Doss

Similar Messages

Is Mapping Lookup table possible with IDOC to FIle scenario

Hi all,
Need suggestion, I am using SP16
My sceanrio is IDOC to FIles, and have to use a Mapping Lookup tables for some of the fields within the mapping...
'Crossref: PlantLoc_to_WhseComDiv. Value mapping lookup to take two fields from SAP and convert to WMS 3-digit value'
How to go with this, since i have checked in SAP library that it is for only RFC,JDBC,SOAP adapters ...
Need u r valuable inputs,
Regards,
sridhar

You can use RFC or SOAP or JDBC lookup in your mapping.Why not?..It does not mean that we use the lookups only in RFC secnarios.You can use them in any scenario.

IDoc Error "" No goods receipt possible for purchase order"

Hi All
I am getting IDoc failed with the error massaeg " No goods receipt possible for purchase order I510954-02 00010
Message type :MBGMCR
Basic type : MBGMCR03
Message no. M7036
Status : 51
Please suggest on this
Thanks
Ajit

Hi
Please go through thid link i think it will help you..
No goods receipt possible in PO
Error - E 036 No goods receipt possible for purchase order
No goods receipt possible for purchase order
Regards
Sharada

Serialization not possible for material number (SHPCON IDOC error )

Hello,
Can any one shed some light on following inbound PGI IDOC (SHPCON) Error from 3PL.
"Serialization not possible for material number XYZ"
Message no. IO205
Diagnosis
The serial number profile of the material does not allow serialization for the operation you have chosen.
Procedure
Maintain the serial number profile.
Additional info
1) Serial number profile is maintained in the material master
2) Serial number populated in the idoc E1EDL11 is not used in any delivery or assigned and it is valid serial number and has equipment master record
3) If i use the same serial number from the IDOC and post PGI manually via VL02N , I am able to post the PGI without any problems and I don;t get the above error
4) IDOC has all the info required , Delivery number,Valid material # , qty,UOM and Line item number of the delivery .
Thanks in advance for your help
GJ

Dear Jalwadi
I got exact same problem. How did you solve it?

BPMOn: Is it possible to send email notification to different groups based on filter value for IDOC?

Hi there,
I have setup the monitoring for idoc through interface monitoring and I am getting the alerts for the same. The alert is generated for different status values for the same idoc. Now my question is, is it possible to send email notification to two different groups based on the status values?? I mean for example , for a single idoc for some status values I want to send email notification to group1 only and for other status values I want to send notification to group2.Any help will be apperitiated.
Thanks and regards,
Rutvik Upadhyay

We currently do not support that level of control for sending email notifications. If you think others are interested in this you should add an idea here: http://forums.adobe.com/community/formscentral?view=idea
We use that to help us prioritize our work.
Thanks,
Randy

Is it possible for jsp(tomcat container) access ejb deployed in sun app se

if it's possible ,how to implement

Hi,
Yes it is possible for a JSP in tomcat container to lookup EJB in sun app server.
Please refer following article for guidelines. If you need further help please revert back.
http://www.onjava.com/pub/a/onjava/2003/02/12/ejb_tomcat.html?page=2
HTH
VJ

Is it possible for XI 2.0 to connect to ECC 6.0 upgraded from SAP R/3 4.6?

Hi,
I just wanted to know whether it is possible for XI 2.0 to be used with ECC 6.0 which is upgraded from SAP R/3 4.6.
If yes, could you forward some links so as to know how.
Thanks,
Fariha

hi,
>>>>Is that Possible..?
yes
>>>Wont there be any additional configuration needed ?
if you use IDOCs then you don't need anything special
Regards,
michal

Acknowledgments for IDoc

Hi,
In an IDoc-PI/XI-External System scenario, are system error acknowledgments sent back to the SAP sender system when system errors occurred during message processing in PI/XI?
If so, in what forms are the system error acknowledgments?
Thanks in advance,
Francis

Ohhh.. i think lot of confusion
I answered earlier also in terms of non SAP systems. Lets talk only in terms of Idoc
In case of idocs, only receiver system decides whether an acknowledgment IDoc should be sent back to the sender based on the ALE configuration (for ALEAUD). So this would only be possible in Idoc - XI - Idoc scenario. In any of the other scenario u will not get ALEAUD back.
In case of External Sys - XI - Idoc, even if Idoc receiver sends back the ALEAUD, BPM would be required to send back the ALEAUD to external system.
In case of Idoc - XI - External Sys, the system ack sent by the External Sys is converted to an ALEAUD message and is sent back to Sender R3 system
Regards,
Prateek

Abstract Interface for IDoc Proxy

Hi All,
Do we need to make Abstract interfaces for IDocs and Proxys too if we want to use them in BPM?
XIer

Aamir,
I agree with u that we can't create proxie's for Abstract interfaces. But consider the case I want to call Proxy inside BPM, is this possible?
Yes its possible. As I mentioned in my previous replies for IDOC's .Similarly for Proxy receiver Interface determination we need to give Actual Inbound Interface name instead of Abstract. MI_Proxy_Abs --> use MI_Proxy_IB . Provided both the interfaces has the same structure.
I hope it clears!!!
Best regards,
raj.

Enhanced Interface Determination for IDOCs

Hi All,
I've a query on the usage of Enhanced Interface Determination for IDocs.
I've to create IDocs based on the condition in the Message Mapping i.e. say if recordtype in the source is A then IDoc1 should be created and if recordtype is B then IDoc2 should be created.
Is it possible to use Enhanced Interface Determination to achieve this??.. Because I was told by someone that Enhanced Interface Determination can't be used for IDoc based scenarios though am using External Definitions for the mapping purpose. Please clarify.
Thanks in advance
Regards,
Joe.

Hi Sridhar/ Bhavesh,
Thanks for your prompt reply. I think I wasn't clear in my previous post.
The scenario is the input file has three different record types (3 different structures) and the IDocs should be created based on the record type. I don't think I can use the condition based scenario as the record types are totally different. Please suggest.
Thanks,
Joe.

Pls send material for idocs in ECC 6.0

Pls send material for idocs in ECC6.0

Hi sitaram s ,
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.
Archiving Processed IDocs
IDoc archiving is a two-step process:
1. Archive the IDoc.
2. After that another job will be generated. You can see in your SARA for your trigger to delete those archived IDocs.
Have a look at transaction WE47, set "Archiving - Possible" for all statuses to be archived. Use transaction SARA with object IDoc to archive. If the above is set then all IDocs are archived the same way.
Transaction SARA works in the following way:
On the main screen enter IDoc as the object. Click on Customising -> Technical settings. This shows the logical filename (configured via transaction FILE & SF01) that will be used to get a filename when writing the archive files. It also shows the document type (that links to an archive via transaction 0AC0) or the archive, depending on SAP version. You can also set the size of the archive files and whether the deletion and storage jobs should execute automatically or not.
On the main screen there are, amongst others, buttons for ARCHIVE, DELETE and MANAGEMENT. When you click on ARCHIVE you will go to a screen where you can create variants, and set the parameters for the archiving job. The EXECUTE button will schedule this job. If the "start automatic" tic for the deletion program was not set in customising, you will need to go to the DELETE button on the main screen to schedule the deletion jobs, after the archive job has finished. This schedules a job per archive file. In MANAGEMENT you will be able to see the statuses of each archive run.
SAP Integration Using ALE(Application Linking and Enabling)
- IDOCS -
http://www.thespot4sap.com/Articles/SAP_ALE_IDOCS.asp
Updating IDoc data in segments,Changing a control record of an IDoc,Getting IDocs linked to Application documents,
Displaying and IDoc in a report,Read IDoc from Database,Creating and sending an IDoc,Update IDoc status on the database
ALE Inbound Pre-Processing
http://www.erpgenie.com/sapedi/idoc_abap.htm
cheers!
gyanaraj
reward points if u find this helpful

Multiple destinations for idoc metadata necessary in AAE

Hello,
we are trying to setup the AAE IDOC adapter in netweaver PI 7.3 sp5.
I am still trying to find my way in the new system, but I get the impression that you can only implement one destination for idoc metadata in the NWA.
This is not suffcient of course since different connected systems can have different custom idoc types.
Is this true? If not how should I configure multiple destinations? the inboundRA resource adapter only points to one destination.
Can I define multiple inboundRA resource adapters or is it possible to have multiple destinations in it?
One parameter of the inboundRA is programID which would lead me to think that multiple destinations based on program id must be possible somehow
See also the saplinks on this:
overviwe
http://help.sap.com/saphelp_nw73ehp1/helpdata/en/c2/91865252c84716b3b8be394851c9c0/frameset.htm
inboundRA
http://help.sap.com/saphelp_nw73ehp1/helpdata/en/c2/91865252c84716b3b8be394851c9c0/frameset.htm
Thanks
Tom

Hi Tom,
It is possible to have multiple destinations and this can be achieved by maintaining the multiRepository parameter value in properties in inboundRA resource adapter. We can specify as many values depending upon the number of destinations. The convention to specify the destination is as follows:
<SID>=XI_IDOC_DEFAULT_DESTINATION_<SID>
Thanks,
Ramya

Fuzzy Lookup Add-In for Excel - Unattended installation

Hi.
I would lige the Fuzzy Lookup Add-In for Excel to be installed silently, but it seems only to be possible for a Per-User installation with the parameter "setup.exe /passive"
I need the installation to be for All Users, but I can´t find any parameter that makes that possible.
/ Torsten

Hi,
Based on your description, your required could be done via logon scripts. Please see the below steps:
1. Open Notepad.
2. Copy and paste, or type, the following:
Const ENGINEERING_GROUP = "cn=engineering"
Const FINANCE_GROUP = "cn=finance"
Const HUMAN_RESOURCES_GROUP = "cn=human resources"
Set wshNetwork = CreateObject("WScript.Network")
wshNetwork.MapNetworkDrive "h:",
"\\FileServer\Users\" & wshNetwork.UserName
Set ADSysInfo = CreateObject("ADSystemInfo")
Set CurrentUser = GetObject("LDAP://" &
ADSysInfo.UserName)
strGroups = LCase(Join(CurrentUser.MemberOf))
If InStr(strGroups, ENGINEERING_GROUP) Then
wshNetwork.MapNetworkDrive "g:",
"\\FileServer\Engineering\"
wshNetwork.AddWindowsPrinterConnection
"\\PrintServer\EngLaser"
wshNetwork.AddWindowsPrinterConnection
"\\PrintServer\Plotter"
wshNetWork.SetDefaultPrinter
"\\PrintServer\EngLaser"
ElseIf InStr(strGroups, FINANCE_GROUP) Then
wshNetwork.MapNetworkDrive "g:",
"\\FileServer\Finance\"
wshNetwork.AddWindowsPrinterConnection
"\\PrintServer\FinLaser"
wshNetWork.SetDefaultPrinter
"\\PrintServer\FinLaser"
ElseIf InStr(strGroups, HUMAN_RESOURCES_GROUP) Then
wshNetwork.MapNetworkDrive "g:",
"\\FileServer\Human Resources\"
wshNetwork.AddWindowsPrinterConnection
"\\PrintServer\HrLaser"
wshNetWork.SetDefaultPrinter
"\\PrintServer\HrLaser"
End If
3. On the File menu, click Save As.
4. In Save in, click the directory that corresponds to the domain controller's Netlogon shared folder (usually SystemRoot\SYSVOL\Sysvol\DomainName\Scripts where DomainName is the domain's fully qualified domain name).
5. In Save as type, click All Files.
6. In File name, type a file name, followed by .vbs, and then click Save. WSH uses the .vbs extension to identify files that contain VBScript commands.
More reference::
http://technet.microsoft.com/en-us/library/cc758918(v=WS.10).aspx
http://technet.microsoft.com/en-us/library/cc784088(v=ws.10).aspx
http://technet.microsoft.com/en-us/library/cc779490(v=WS.10).aspx
If you have further question about logon scripts, I recommend you post the question to below forum.
https://social.technet.microsoft.com/Forums/scriptcenter/en-US/home?forum=ITCG&filter=alltypes&sort=lastpostdesc
Regards,
George Zhao
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Steps for Idoc to EDI Subsystem

Hi all,
Can anyone tell me the steps that i have to worry about to send an idoc immediately to EDI Subsystem
I mean what all things i have to specify while creating ports and partner profiles etc
Thanks

Sending Order Confirmations by EDI (SD-SLS)
Use
By setting up and using the Electronic Data Interchange functions in the R/3 System, you eliminate the need to print documents and send them through the standard mail system. Instead, you send the information electronically. This method is more practical, convenient, and allows you and your customer to process data faster.
In this EDI scenario, you process and send order confirmations to a customer's R/3 Purchasing system.
Prerequisites
Application
Customizing
To process outbound order confirmations, you need to make all of the necessary EDI settings in Customizing for Basis. You make settings for output control in Customizing for Sales and Distribution.
Output Control
The standard SD condition components are:
Condition component     Value
Sales document type     AA
Output determination procedure     V10000
Condition type     BA00
Transmission medium     6 (EDI)
Access sequence     0001
Processing subroutine     Program RSNASTED, form routine EDI_PROCESSING
Partner function     SP (sold-to party)
Application     V1
Condition records for outbound order confirmations are maintained in Customizing for Sales and Distribution. Choose Basic Functions  Output Control  Output Determination  Output Determination Using the Condition Technique  Maintain Output Determination for Sales Documents.
IDoc Interface
Define the EDI partner profile for your partner (transaction WE20) by entering the following data for the outbound parameters for partner profiles and the additional profiles for message control:
Field     Value
Message type     ORDRSP
Partner type     KU (customer)
Partner function     SP (sold-to party)
Receiver port     e.g. SUBSYSTEM
Output mode     e.g. Transfer IDoc immediately
Basic type     ORDERS04
Process code     SD10
Activities
Create an order. When you save the document, the system uses your settings in output control to find the appropriate condition record and send confirmation of the order by EDI. To review and maintain output data in the document, choose Extras  Output  Header.
Receiving Acknowledgments via EDI (MM-PUR-GF-CON)
Use
You have arranged with your vendor that that latter is to send you acknowledgments in respect of purchase orders or outline agreements received from your company. (Note: both kinds of acknowledgment are generally referred to as "order acknowledgments" in the system. The corresponding EDIFACT term is "order response" (ORDRSP).)
You have the option of working exclusively with acknowledgments. The acknowledgment is then purely informative in nature, since only the acknowledgment number is recorded in the system.
If you wish to receive different kinds of vendor confirmation, such as both order acknowledgments and shipping notifications (also known as advance shipping notices - ASNs), it is possible for quantities and dates to be entered in the system automatically).
For more information on this topic, refer to the MM Purchasing documentation ( Confirmations from the Purchasing Viewpoint and Receiving Confirmations via EDI).
Prerequisites
Application
To work with several categories of vendor confirmation, you must:
u2022     Enter a confirmation control key on the item detail screen
u2022     Set up the confirmation control facility in Customizing for Purchasing (Purchasing  Confirmations  Set up Confirmation Control). There you can specify the order in which you expect confirmations from your vendors, for example.
Under Confirmation sequence, you can:
u2022     Specify tolerances for date and price checks
u2022     Allow vendor material changes (VMat indicator)
u2022     Adopt vendor price changes (Price indicator)
Do not use a confirmation control key if you work exclusively with acknowledgments.
IDoc Interface
You have made the following settings for your EDI vendors in Customizing for Purchasing (Purchasing  Messages  EDI  Set up Partner Profile):
Parameters for Inbound Messages
Field     Value
Partner type     LI
Partner role     LF
Message category     ORDRSP
Process code     ORDR
Processing     Initiate immediately or process via background program
Activities
When an acknowledgment is received in the form of an incoming EDI message, the system checks whether a confirmation control key has been entered in the relevant PO or outline purchase agreement.
u2022     If there is no confirmation control key, only the acknowledgment number is entered on the item detail screen.
u2022     If there is a confirmation control key, the system updates the confirmation overview. That is to say, the dates and quantities set out in the acknowledgment that has just been received are recorded and taken into account in the overview. To view acknowledgments that have been received, choose Item  Confirmations  Overview from the item overview. Column C (creation indicator) contains the value 3, meaning that the acknowledgment was received via EDI. The system also enters the IDoc number in the External document column.
An IDoc can always acknowledge one purchase order only. The acknowledgment relates to the PO item, not to any individual schedule lines.
Exceptions
When an acknowledgment is received via EDI, the system automatically checks quantities, prices, and dates. In checking quantities, it applies the over- and underdelivery tolerances set for the item. You can set tolerances for prices and delivery dates in Customizing for Purchasing under Set up Confirmation Control.
The tolerances you define apply to all vendors. Using the enhancement MM06E001 provided by SAP, you can specify that the tolerances do not apply to certain vendors.
If the acknowledged quantities, prices, and dates vary from those set out in the PO or purchase agreement, the system issues a warning message. In this case, the purchasing document is not updated.
For more information on this topic, refer to the section Error Correction (Receiving Confirmations via EDI) of the MM Purchasing documentation.
Sending PO Change Notices via EDI (MM-PUR-PO)
Use
This section describes how to transmit a change notice relating to a purchase order that has already been sent to a vendor.
The function corresponds to the transmission of a purchase order via EDI.
Prerequisites
Application
You have already successfully transmitted the original purchase order to the vendor via EDI.
Message Control
You have created message condition records for your EDI vendors (Purchasing  Master data  Messages  Purchase order  Create).
Use the message type NEU to transmit PO change notices.
IDoc Interface
You have made the following settings for your EDI vendors in Customizing for Purchasing (Purchasing  Messages  Set up Partner Profile):
Parameters for Outbound Messages
Field     Value
Application     EF ( Purchasing: purchase order)
Message category     ORDCHG
IDoc type     ORDERS02 or ORDERS04
Process code     ME 11 (ORDCHG: PO change notice)
If you wish to transmit PO conditions or texts to your vendor, you must create an IDoc view. For more information on this topic, see Sending a Purchase Order via EDI.
Activities
Change an existing purchase order via Purchasing  Purchase order  Change. Make the necessary changes and save the PO.
The new message is compared with the last successfully transmitted message. PO change notices indicate whether any new items have been added to the PO, and/or whether any already transmitted items have been changed.
When the message is transmitted, only those changes that are simultaneously new and print-relevant are included. The system sets the change indicator for the new message. To check the change indicator, choose Header  Messages in the PO item overview.
See also:
MM Purchasing: Creating a Purchase Order
Cross-Application Components: Customizing Message Control in Purchasing (MM): Example: Purchase Order
Receiving Order Changes by EDI (SD-SLS)
Use
In this EDI scenario, you receive and process order changes sent by a customer from an R/3 Purchasing system.
Prerequisites
Application
General
You can receive and process order changes in your system only on the basis of an existing order.
Customizing
To process incoming order changes, you need to make all of the necessary settings in Customizing for Basis. There are no special settings for Sales and Distribution.
IDoc Interface
Define the EDI partner profile for your partner (transaction WE20) by entering the following data in the header and detail screen for inbound parameters:
Parameter     Value
Partner type     KU (customer); if the IDoc is sent from an R/3 system via tRFC (in a typical case with ALE scenarios), enter LS for logical system!
Message type     ORDCHG
Process code     ORDC
Processing     Process immediately
Allowed Agents     Enter an R/3 user or an organizational unit, for example.
Activities
Inbound Processing
The IDoc interface receives the IDoc and reviews its control record. According to this record and the corresponding partner profile, the IDoc is transferred to the function module IDOC_INPUT_ORDCHG in Sales and Distribution. The ALE services are called.
The system processes the IDoc in the background, using the data records in the IDoc to determine the relevant order.
If processing is successful, the system updates the sales order. The IDoc is sent back to the IDoc interface which updates the status records in the IDoc.
Exception Handling
If it cannot determine an order, or if an error occurs in processing, the system determines the relevant agent(s) and sends a workitem to the integrated inbox(es). An agent can pick up the workitem to process the IDoc or simply end processing.
To display an IDoc for order changes, choose Environment  Display facsimiles in the order. The system displays a dialog box of object links where you can choose Linked IDocs.

Did anyone know how to update status for Idoc Finsta01

Hi ,
Did anybody did updating idoc status and message for idoc type FINSTA01.
In Lockbox idoc_input_lockbx.
If any BADI avilibale fr this to update.
Thanks,
Madhu

Option 1:
See SAP Help as below you will get the idea-
Certain IDoc statuses are classified as archivable in the standard system, while others are not. You can display or change this classification.
The current status of an IDoc must be archivable before the IDoc can be archived.
Procedure
Choose SAP Menu -> Tools -> Business Communications -> IDoc Basis -> Control -> Status -> Maintain Status Value.
To change entries, choose .
Select the required status. By double-clicking you can call a detail screen, in which you can display or change the archivability.
By using or you can display or change all statuses one after another.
Option2: I think it might be possible using generate status file for the outbound IDOC and then change the status in the file further process it. But I am not sure, I just had a look at the Xns in WEDI and made this story
Thanks,
Naren

Lookup is possible for IDOC?

Similar Messages

Maybe you are looking for