IDOC testing for Lockbox

Hi Experts,
Can someone send me the sample file of Lockbox data for testing IDOC processing (email). I do not know what to fill in these parameters in WE19 (Finsta01). I created one customer invoice and do have all the lockbox information.
These are the parameters to fill for lockbox test in WE19
EDIDC      0000000000000000
        E1IDKU1
        E1EDK03
        E1EDK02
        E1IDB02
        E1EDKA1
        E1IDPF1
        E1IDKU7
Regards,
Sim
[email protected]

Hello
EDIDC 0000000000000000 is for the port partner number etc
E1EDK03 contains the year month date and time
E1IDLB1 is the lock box number which the bank sends
E1IdBq2 is the bank routing number and the acocunt number
and another line of E1IdBq2 is the customers bank details which are maintained in the customers master
E1EDQ02 is the check number with which the payment is made
E1IDQu5 is the amount on the check
E1Idru5 is the invoice amount
and E1EDR02 is the invoice number in SAP
Assign points if helpfull

Similar Messages

Idoc test scenario for MM invoice verification

Dear Experts,
I am doing a scenario for testing the inbound process for Invoice ( MM ).
If any body has done this test idoc prcoessing for the scenario, i need your valuable help in how to go about this.
In simple, how to do the WE19 for MM invoice verification.
Regards
RAj

hi,
Pls check this link,Hope it helps
Test IDOC inbound processing in WE19
No status record was passed to ALE (Working fine in WE19)
thanks.

IDOCS for Lockbox

Dear All,
can anybody help me with any readables on creating idoc for lockbox and how it is used ?
best regds
Subha

Hi Das,
Sorry for missing of link. PFA the links for your easy reference.
Lockbox Processing
Lockbox Configuration
Thanks & Regards,
Lakshmi S

XI testing for two SAP R/3 systems with same system id/logical system

Hi
We are currently in the process of upgrading our R/3 4.7 to ECC 6.0 and plan to maintain dual landscape for DEV & QA (4.7 & ECC 6.0) for a period for testing and maintaining existing applications for fixes etc. The second DEV & QA (upgraded to ECC 6.0) are copy of respective systems and these systems are created automatically under technical systems in SLD by auto update (RZ70).
The question is, can we use the same XI system for testing inbound/outbound interfaces for both the systems i.e 4.7 & ECC 6.0 at the same time. I am aware of the fact that XI Technical/Business sytems dependent on unique logical systems, so we cannot create new business system for the upgraded DEV-II ECC 6.0 system.
For your information, we have two slds (one for XID/XIQ and second one for XIP).
What are the options without disturbing & maintaining the current XI system set up?
1) Can we change current Business systems e.g DEV010 to use new technical system i.e DEV-II ECC 6.0 for testing for a period and switch it back to DEV-I 4.7 technical system?
2) or change logitical system name of DEV-II ECC 6.0 and create new business sytem in SLD without interfering the existing setup and modify/create interfaces to use this new business system?
3) Do we need to refresh cache from time to time in XI ?
4) Any other implications
We will be upgrading XI to PI 7.1 after ECC 6. 0 Upgrade.
Any views on this would be highly appreciated.
Regards
Chandu

Hi
Technical System was created in the SLD automatically after RZ70 configuration in the new DEV-II system. We then modified Business System to use the new Technical system and carried out following steps:
1)     Original Idoc metadata was deleted from XID
2)     The port definition was deleted
3)     A new port definition was created for new system
4)     The metadata for each idoc type used was re-created in IDX2 , using METADATA -> CREATE
5)     This brought in all known versions of the idoc segments, including the 7.1 version.
I have already checked the guides suggested for our upgrade and we are thinking of going ahead with fresh installation and migrating the interfaces.
Regards
Chandu

RSAR238 : IDoc type for source system T90CLNT090 is not available

Hi all,
I am working on ECC 6.0. Have created a ODS object using RSA1OLD. While activating the ODS, am getting this error:
1. Error:
R7I028
Object could not be activated
2. Error:
RSAR238
IDoc type for source system T90CLNT090 is not available
Error when creating the export datasource and dependent objects
Kindly help me with this error.
Thanks and regards,
Dhanapal

Hi,
Check the same in SDN..
Object ZDUMMY could not be activatedMessage no. R7I028
Re: DSO Activation problem
http://sap.ittoolbox.com/groups/technical-functional/sap-bw/test-cases-for-module-human-capital-management-1425016
http://sap.ittoolbox.com/groups/technical-functional/sap-bw/idoc-type-for-source-system-t90clnt090-is-not-available-message-no-rsar238-1431565
Thanks
Reddy

Idoc type for personnel area

Hello Everyone,
Could someone please let me know Idoc type for sending personnel area details.
We want to send Idoc whenever a new personnel area is created / changed in SPRO.
Best Regards,
Priyanka Gupta.

Hello Priyanka,
Use the standard idoc Message Type HRMD_A for master data and then you can included the following code in FILTER_VALUES_SET method of the BADI implementation by T code BD64
CHECK OTYPE = 'P '.
*SELECT * FROM PA0001*
INTO PA0001 WHERE PERNR = OBJID
AND BEGDA <= SY-DATUM
AND ENDDA >= SY-DATUM.
record is valid today, no authorization check*
EXIT.
ENDSELECT.
IF SY-SUBRC = 0.
FILTER1 = PA0001-BUKRS. ELSE.
CLEAR FILTER1.
ENDIF.
Note: the record you are testing for has your desired company code PGPB.
regards

IDOC WMMBID02 for Outbound

Hi,
I am trying to configure an outbound IDOC for GI/ GR. I was told to use WMMBID02 for this, but it uses FM L_IDOC_INPUT_WMMBXY.
Has anyone tried to use IDOC WMMBID02 for outbound? I want to use this for a particular GI with Material Document as a parameter.
Thanks.
Kenny

Hi Ferry,
Thanks for the reply.
I cant seem to make this test program work. I just put the Mat Doc Num and the Year then ticked direct processing. It then shows "Check your entries".
Please help.
Thanks.
Kenny

MIRO Invoice - Testing for INVOIC02 in EDI scenario

Dear Experts,
I am doing a scenario for testing the inbound process for Invoice ( MM ).
( Sending system is LS of XI and receiving system is LS of R/3)
If any body has done this test idoc prcoessing for the scenario, i need your valuable help in how to go about this.
In simple, how to do the WE19 for MM invoice verification.
When I am doing the test scenario, I am getting an error.
LS 'Vendor No' company code not maintained.
But if I go to OBCA there no LS for Vendor.
So, can anyone guide me what should be the value for the below segment E1EDKA1 ( PARVW and PARTN) .
Also the value for the segment E1EDK14 .
If any one provide me moredetails about this , i would be grateful to you.
Regards
RAj

Self Resolved. Config missing in OBCA

Idoc ORDERS05 for PO Outbound for the Output type ZSUS.

I have a standard Idoc ORDERS05 for the PO.
I have Extended this Idoc and Created a Z- Segment below E1EDKA1 which is ZE1EDKA1.
There are Four Fields in it. i.e. ZZFNAME, ZZLMAE, ZZEMAIL & ZZADDRESS.
When I create the PO using ME21N OR Change using ME22N and use the MEssage type ZSUS which is Configured in the NACE T-Code.
The Idoc Just does not get triggered . I tried to do the same through the test tool. WE19 but yet the Idocs gets Created but the Z-segment does not get populted nor is seen.
I have writtem my code in the Exit 'EXIT_SAPLEINM_002' and have poulated the above mentioned four fields.
But the Idocs just does not reach the user Exit and hence these four fields do not get populated.
I have done the neccessary configuration in WE82 and also in WE57.
Can u please provide me with the Solution.
Regards,
Deepak.

Hi,
Use table NAST

IDOC testing: how to upload sample IDOC xml file while outbound IDOCtesting

Hi experts,
can any one tell me , how to upload a sample XML idoc xml(data) file while Outbound IDOC testing;
in WE19 tcode ( insted of manually entering the sample data, i have to import the sample XML/text file into the idoc fields). say IDOC is MATMAS.
Thanks in advance;
Kumar

Hi Asit Purbey,
can you clearly explain, how to upload the file and how can i genetare the IDOC no?
i have seen that function module IDOC_XML_FROM_FILE, in that it is required a port no, what exactly it is, and what type of port is it?
suppose i am having a XML/TEXT file with IDOC data, how can i upload it into the server and how can convert it into the IDOC and how can i generate the IDOC no for outbound testing?
Thanks,
Anil

IDoc processing for same message type but diff extensions

Hi
I want to send idoc when a material is changed. Everything is in place and have also done a test scenario. In partner profile i had the message type linked to basic type and tested which is fine. Now i wanted to have one more idoc created for another extension having the same basic type and linked to the same message type. Have maintained the same in WE20 but when i executed BD10 i could only see one idoc been generated but i need to see two idoc (one for basic type and another for the extended) not sure where i'm missing. any pointers on it pls?

Hi ,
if you want to trigger the idoc two times for basic type& Extension..
1 ) you need to maintain WE20 Partner Profiles (This is good already you did)
--> But the Output type for Bsic type & extension type is same so output type is triggered Once so idoc is created One.
2) try to create another Output type in T-code NACE for extension then two Idocs is created one for Basic and another for Extension.
Regards,
Prabhudas

Reg: RFC / IDOC required for doing CIDX Scenario

Hi! Gurus,
This is Amar Srinivas Eli. I have task here to work and implement CIDX Scenario succesfully. There are some business cases as per the CIDX standards from that I was selected one Business case i,,e, FORECASTING.
But inorder to implement that scenario I need some RFC's or IDOC lists from SAP side whether it may be a source or target side..what ever it may be...and other side will be CIDX format.
Here I need your help in the below mentioned tasks. Kindly help me out in a detailed step by step guide and do the needful to me.
1. How to get RFC / IDOC name from R3 System and I know that I can get RFC from SE37 and IDOCs
from WE05 but I need whether all the required fileds are statisfying in the RFC's or not.
2. My first preference is only for STANDARD SAP RFCs or IDOCs.
3. Please let me know how to see the inner fields present in those RFC's
4. ALso please provide any configuration guide which contains screen shots if you already worked
earlier on CIDX Scenario I mean step by step and also for testing
5... tell me if there is any other tool other than STK kit for testing CIDX messages.
6. Is there any Freeware STK tool kit is there or not...
Also share your experience and errors that you have faces while doing this CIDX Scenario.
Regards:
Amar Srinivas Eli

Hi! All,
Thanks for your fast response..
Hi! Raja,
I gone through your points. Here I have few doubts on those please clarify that.
1. Coming to testing i didt used any testing tool , but you can comre your output using XML Spy or Stylus studio.*
*CIDx Documents,you wil find in SDN please search in SDN.
Means Without using STK Tool or else some other tool How can I get the CIDX response for my request in the Testing environment. See I am not doing this in real time I am trying to findout the solution for Business cases so I need one testing environment tool right ? Is that ALTOVA XML spy will give no right ?
Note: You told that you have done that business case IDOC--CIDX Order change / req Will you please share the information documentation I mean step by step procedure for end to end doc...based on your scenario ?
2. I know those R3 and PI settings I mean configurations means ports and RFC destinations and all those..but only thing I dono is "How you got that IDOC I mean on what basis and how did u search the IDOC?"
3. See Here I am working on topic FORECASTING it includes so many sub tasks like Deman PLan req and response, supply plan req and response and replenishment order and etc....so based on that how can I get those related RFC's or IDOC's in order to communicate from R3 Side
If Suppose I have seen one RFC/IDOC and for example out of 10 fields few are there in one IDOC and another few are there in another IDOC then in that case I need to go for Multimapping IDOCs I mean 2 Senders to one Receiver if yes Is it possible?
My first requirement is based on the above mentioned business cases how can I get the corresponding RFC's or IDOCs ?
Regards:
Amar Srinivas Eli
Edited by: Amar Srinivas Eli on Jan 5, 2009 12:19 PM

Inbound idoc testing via partner profile

i want to test inbound idoc testing via partner profile.
the problem is i its generating idoc no and giving a message like
"idoc no 12453152.. is saved but cannot or shd not be processed".
what does that mean ..
how shd i veiw properties of partner p[rofiles

i am getting thid message from we 19 ..
in that i am creating a sales order...
i am clicking on startinboung button on application tools bar.
this is an information pop up window ..
if i press f1 on that ..
help says that ...may be you cannot process the idoc immediatly...
check for partner profiles

WMMBID02 idoc type for 313 movement

Hi,
I want to integrate two step movement (313-315) in a third party system to SAP. Now we are using WMMBID02 idoc type for stock transfers but when I tested movement type 313 I got an error ""you have entered a movement type that has not been defined for this transaction/event.
Does it mean that WMMBID02 idoc type is not used for 313 stock movement?
Which idoc type should we use?
Thank you

Hi,
Problem is happening becuase of Transaction code used in IDOC header segment, try checking the tcode used and whether its valid for the mvt 313 (u can check this in transaction code OMJJ),
if i can guess it right, u should try using MIGO in your idoc, if it doesn't work try using MB1B,
IF you are in version 4.6c or below, then MB1B will work (MIGO is allowed for transfers only after 4.7 and above)
hope this helps
Reg
Dheeraj

Idoc Testing! Need help!

Hi!
 (Please give answers specific to my question & pls read below)
 i want to test idoc outbound as well as inbound.
First Consider inbound,
 I ve read previous posted threads it was mentioned goto>we19> give idoc no
I want to know what is idoc no how we get idoc no for the idoc.

Then i know the steps...
Now Outbound,
How to test outbound idoc -- i want to know how my posting program has correctly generated idoc to ale layer.
I want this in complete detail.
 Thanks!
 Rahul.

Hi Rahul,
idoc structure
http://www.sapbrainsonline.com/ARTICLES/TECHNICAL/idoc/SAP_IDOC_structure_introduction.html
What is Idoc?
I give overview of IDoc terminology and how IDocs work in an enterprise will clarify the process
SAPs presence in the IT world is justified by a central premise: It turns a companys many individual systems into one, big supersystem. More than a linking together of applications, SAPs implementation causes a redirection of the flow of information through a company and its partner companies that enhances the potential of its business functions.
This flow of information is enabled by a core element in SAP technology: the Intermediate Document, or IDoc. Technically, the IDoc is an example of Electronic Data Interchange (EDI). Unlike conventional EDI, IDocs are not based on a descriptive language.
The IDoc concept borrows the best features of EDI and combines them with the best features of conventional transaction file formats. The result is a lean data transport mechanism that is the engine of SAP data flow, tying together applications, databases, companies, and networks. Here is a look at the makeup of IDocs within the application architecture.
Form and content: IDoc terminology
As is often the case with proprietary technologies, SAP assigns specific, object-oriented meanings to familiar terms. When referring to IDocs, the term document refers to a set of data comprising a functional group of records with a business identity. (For example, all the data in a purchase order, or all the profile information of a supplier in a supplier master record.)
A message refers to the contents of a specific implementation of an IDoc; its a logical reference. This differs from a reference to the IDoc itself, which specifies the messages physical representation. Think of it this way: If youre watching a parade pass by, the mayor waving to the crowd from his limousine is the message, and the mayors limousine (which is specific to the mayor) is the IDoc. Youre building a logical object, and the IDoc is both its container and the vehicle that moves it.
The IDoc control record
Each IDoc has a single control record, always the first record in the set. The structure of this record describes the content of the data records that will follow and provides administrative information, such as the IDocs functional category (Message Type/IDoc Type), as well as its origin (Sender) and destination (Receiver) as in conventional EDI (see Figure A).
Figure A
IDOC number Sender Receiver Port Message type IDoc type
1234567890 R3NYC R3LA FILE INVOICES INVOICE01
This cover slip format informs the receiving system of the IDocs purpose, and the receiving system uses it to determine the correct processing algorithm for handling the arriving IDoc.
Data records
The data records following the control record are structured alike, including two sections: a segment information section and a data section.
In the first part of a data record, the segment information section describes the structure of the data that follows, for the benefit of the IDoc processor. There is a segment name (like an EDI segment identifier) that corresponds to a data dictionary structure to which the IDoc processor has access. The remaining information is useful for foreign systems, such as a partner companys Oracle system, which has no such data dictionary.
The second part of the record is the data itself, a storage area of 1,000 characters.
Status records
If youve ever ordered a package from a faraway location and tracked its progress using the Internet-based tracking utilities now provided by most major parcel carriers, youre familiar with the list of stops and transfer points through which a package passes on its way to you.
This collection of records is exactly what youll see in an IDoc that has begun its work. Following the data records in an IDoc, status records accumulate as an IDoc makes its way from one point in a process to another.
Typically, an IDoc will acquire several of these records as its does its job. They are simple records, consisting of a status code (there are more than 70 codes, covering a broad range of conditions and errors), a date/time stamp, and some additional status information fields for system audit purposes. In addition, as errors occur in the processing of an IDoc, status records (see Figure B) are used to record these errors and the date/time of their occurrence.
Figure B
(Display Status Record)
IDoc number 0000000000123456
Direction 1 Outbound
Status information
 38 IDoc archived
(additional descriptive text)
Log time
 Date 6-30-02
 Time 14:35:21
Portion of IDoc status display
IDoc Base
IDocs, as data formatting tools, enable the easy sharing of data between databases and applications within a company as well as being an efficient data courier between companies. Typically in SAP, a database of IDoc definitions exists, to which any application may have access.
This IDoc Base gives all the applications and processes in your company domain the capacity to send, receive, and process a document in a contextually appropriate way, without doing anything to the data. For example, a purchase order IDoc can filter through every process it touches, passing from system to system, accumulating status records to track its progress.
Every department using the data can use it appropriately without any cumbersome intermediate processes, because each department draws its key to interpreting the IDoc from the same source.
Multiple messages
One cumbersome feature of conventional EDI is the embedding of more than one functional record type in a document. The unwieldy X-12 888 Item Maintenance transaction set is an example: It purports to handle so many different configurations of product master data that it is horrifically difficult to integrate into an existing system.
IDocs, on the other hand, handle multiple messages with ease. Given the centralized IDoc interpretation that SAP provides to all its parts, its no problem to define an IDoc that will contain more than one message, that is, more than one data record type.
A customer master IDoc, for example, may contain customer profile information records for a customer with many locations. But it may also contain location-specific pricing information records for that customer in the same document. This is an incredibly efficient way of bundling related records, particularly when passing large amounts of complex information from system to system (see Figure C).
Figure C
CONTROL RECORD
DATA RECORD - CUST PROFILE LOC #1
DATA RECORD - CUST PROFILE LOC #2
DATA RECORD - CUST PROFILE LOC #3
DATA RECORD - CUST DISCOUNT STRUCTURE LOC #1
DATA RECORD - CUST DISCOUNT STRUCTURE LOC #2
DATA RECORD - CUST DISCOUNT STRUCTURE LOC #3
STATUS RECORD
STATUS RECORD
STATUS RECORD
Records in a multiple-message IDoc
Final thought
There is no mastering SAP without mastering its workhorse, the IDoc. ERP environments utilizing SAP and similar platforms are made necessary in the first place by the increasing demands of ever more integrated business relationships. IDoc technology addresses this trend with a simple but powerful design philosophy: Data is no longer something to be stored; its something to be moved.
And
These links give u complete details abt idocs testing
Test Tool
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b80f643d711d1893e0000e8323c4f/content.htm
Status Monitor for ALE Messages
http://help.sap.com/saphelp_nw04/helpdata/en/d4/0d67e4d85511d2a6080060087832f8/content.htm
Regards ,
Kumar.

IDOC testing for Lockbox

Similar Messages

Maybe you are looking for