SAP Lockbox Processing (EDI 823) via FINSTA01 IDoc

I am trying to implement lockbox processing in SAP using the FINSTA01 IDoc. I have not found any documentation regarding the data mapping. Does anybody have experience with this? If so, I could really use a sample data mapping document.
Any help would be appreciated.

Hi,
Sorry,
Three times the same URL has copied,
Click to the URL and check :
http://help.sap.com/saphelp_erp2005/helpdata/en/57/f1fc3768b56d00e10000009b38f842/frameset.htm
1) Importing Lockbox Data
2) Postprocess Lockbox Data
This might help you,
http://ifr.sap.com/catalog/query.asp?namespace=urn:sap-com:ifr:FI:470&type=idoc&name=FINSTA01
Regards
Agasthuri Doss

Similar Messages

Lockbox with EDI 823

Here is the process we follow:
We get EDi823 from the Bank. we create the I-doc FINSTA01 which creates the data in the Payment advice. The customer pays by 2 fields- Actual Invoice number and reference which is a sales order number.
What are the settings we require in the Selection rule or FLBP to check for both the fields? we created a new selection field with Document number and Reference field and attached it to the customer master but that is not working and FLBP is putting everything "on Account".
Any Suggestions.

Hi Nitin
When you create the selection rule, you can prioritize the fields. In your case, document number should be first and then the reference.
Also, in the config for selection rule, the system gives the options for external selection filed and the selection field. So, you need to take a look at the payment advice and confirm that the document number is getting populated in the BELNR field of the payment advice and the order number is actually getting populated in XBLNR.
If you EDI 823 is mapped to populate the above values in some other fields in the payment advice, your config should reflect the same. Otherwise the system would not match the open items.

EDI 823 to iDoc FINSTA01

I am trying to map EDI 823 file to iDoc FINSTA01.
I mapped as much as I know, but I am getting following errors when I test it:
- External transaction is missing for determining the posting rule
- Bank statement date is incorrect: 00000000
Anyone seem these errors?
Anyone know what I need to fix to get rid of these errors?
Any help can be really appreciated.
Thank you,
John

Hi,
Can you give the procedure to configure EDI 823 and the bare minimim segments with fields that are required to be filled if you have solved the issue you got earlier.
Thanks & regards,
raj

SAP ABAP and EDI/ALE/IDOC

Hi gurus,
I am an ABAP consultant and I am trying to learn EDI/ALE and Idoc, but I am not sure where to start with and what all do I need to cover in it. So can you please tell me how to proceed and what all is reqd. to know about EDI/ALE and Idoc for an ABAP guy and it will be great if you can also send me some documentation .
Thanks,
Rajeev !!!

Please check this online document for ALE and IDoc.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
EDI
Electronic Data Interchange
Cross-company exchange of electronic data (for example business documents) between domestic and international business partners who use a variety of hardware, software, and communication services. The data involved is formatted according to predefined standards. In addition to this, SAP ALE technology is available for data exchange within a company.
Refer
http://www.erpgenie.com/sapedi/index.htm
http://help.sap.com/saphelp_nw04/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm
https://www.2020software.com/products/Fourth_Shift_Edition_for_SAP_Business_One_Electronic_Data_Interchange.asp
http://downloads-zdnet.com.com/SoftwareandWebDevelopment/SoftwareDevelopmentTools/ElectronicData+Interchange/
http://www.erpgenie.com/sapedi/index.htm
http://www.kostal.com/english/downloads/EDI_AGB_eng.pdfd
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.
EDI FLOW :
Here is some thing which helps you and here the purchase order is taken as example too..
Electronic Data Interchange, or EDI, is the electronic exchange of business data. Using a standard format, EDI provides a method of transmitting business data from one computer to another, without the need to re-key data. This electronic link can result in more effective business transactions. With EDI, paper documents such as invoices can be replaced with electronic transmissions, thus time is saved, and the potential for error is minimized. Data can be exchanged at any time. Related business expenses, such as postage, printing, phone calls, and handling, can also be significantly reduced. EDI can aid in the support of manufacturing efforts, such as Just-in-Time and Third Party Warehousing, and financial efforts, such as Electronic Payments.
What parts of the business cycle can be supported by EDI?
Any business documents that are currently exchanged using paper can be converted to an EDI. Standards. Standards include ANSI X12 and XML/EDI are primarily used in the United States, while EDIFACT is used in Europe and Asia.
How does EDI get started?
EDI gets started when one company contacts another expressing interest in trading business documents electronically using Electronic Data Interchange. The two companies must first determine each other's EDI capabilities. If you do not already know your EDI capabilities, we have prepared a questionnaire to help you determine them. If you are already EDI capable, we will coordinate with your technical staff to determine a testing plan. Upon completion of testing the EDI documents, the appropriate business personnel will set a production start date to begin the exchange of EDI business data. If you are not EDI capable, we recommend you first obtain a commitment from your upper management. Your company will need to allocate resources and capital for software, hardware, testing, possible programming, and training.
What is the flow of EDI?
The flow of EDI depends on the sophistication of your systems and your EDI software. If you have internal purchasing/order entry systems, you will need interface programs that can extract and insert data out of and into these systems. EDI programs that interface with your internal systems are preferred over software that requires re-keying of data. Embassy Software specializes in seemless interface between EDI and your back office systems. Using a purchase order as an example of a business document your customer would send that PO electronically (850) to you. It could be sent either through a VAN (Value Added Network) or through an FTP server. You would take that 850 and convert it either into and ODBC database, a flat file or XML document to be imported into your Order System with the use of EDI Software such as PassportXchange.. Using EDI communication software, which is part of the PassportXchange package you would pull down data at set intervals from the VAN or FTP. These documents are then processed through EDI translation software and output to our order entry system. Finally, an EDI document called a functional acknowledgment (997) is sent to your customer.

Error: EDI: Error while assigning IDoc number

Hi Everybody,
using XI 3.0 on Linux 64 bit SLES9 with Oracle I got some probleme sending messages from mq series to sap:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30"
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>EDI: Error while assigning IDoc number</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: EDI: Error while assigning IDoc number</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
What is missing here?
Kind regards,
Michael

Hi Jayakrishnan,
thanks a lot for your answer.
SM59 is working finde. In IDX1 I got the the correct RFC destination entered and a double click works fine also.
The other way around R3 -> XI -> mq series is working fine. Here we are trying mq -> XI -> R3 and it stops sending from XI to R/3.
How to check the IDOC type?
Regards,
Michael

EDI 821 and EDI 823 field mapping file and basic IDOC type and message type

Hi All,
We are facing some issues regarding EDI 821 and EDI 823 file mappings.
We are mapping EDI 821 and EDI 823 transactions into SAP using IDOCs. Currently we are using the below entries
EDI 823 - Lock Box
Basic IDOC type - FINSTA01
Message type - FINSTA
Process Code - FINS
The problem is we are able to get the IDOC into SAP with status red and the various errors were due to not able to create the lockbox entry in SAP and once we got yellow status also but the lock box entry was not created and the errors are like No Conversions,no header etc.
EDI 821 -
Basic IDOC type - PEXR2002
Message type - PAYEXT OR REMADV
Process Code - PEXC OR REMA
We are facing the same problem here also and the internal payment order is not creating in SAP and IDOC was generated with yellow status and red status.
We are trying different combinations but nothing is working so far.
I need the following things to proceed furthur.
1)Are the IDOC , Message and process codes are correct that I am using now for both EDI 821 and EDI 823
2)If those are not correct, can you please let me know the correct entries
3) Please provide me the field mapping if any one of you have worked earlier for both the above IDOC and message type or new ones and we have one field mapping now but if you can send it to me then I can re check it.
4) Do we have to create any configuraion or customizing in SAP to create the IDOC in green status and if so please let me know the customizing steps and procedures for both EDI 821 and EDI 823.
thanks in advance for all your help.
Please let me know if my question is not clear.
Thanks,
Ramesh.

Hi Ramesh,
I believe you are using those interfaces with the business partner type as Bank, Whatever idoc type, message type and process code you have used are perfectly correct.
First of all did you enable your bank for EDI, the house bank has to be EDI enabled first then only your idoc's can be processed, talk to your fi functional consultant and he might help you.
Are you can give me the exact error and i can help you as well.
Thanks,
Mahesh.

Payment Advcie - EDI 823 (Lockbox - Incoming Payment)

Hello,
In process of testing EDI 823(Lockbox u2013 Incoming Payments) using testtool, Idocs are been successfully processing when an attempt is made to post the incoming customeru2019s payment for an open invoice (Basic type u2013 FINSTA01, Message type u2013 LOCKBX). Payment advice note is being generated for the successful processed Idocs.
Then we ran a report RFAVIS40 in SE38 which basically selects the payments advices and then posts the clearing document. In the process when we are trying to execute the report for the generated payment advices u201CFor document type DZ, an entry is required in field referenceu201D this is the message we are getting.
Manually I execute the same payment advice number using FBE2. When I enter the info in u2018Payment totalu2019 and u2018Payment doc.nou2019. at the Header level of FBE2 and then I run the report again, invoice documents are getting cleared.
What config settings require to automate this functionality? OR Am I missing any mandatory field information at the time I process Idoc? OR System would work only in this manner?
Please pass your comments.
Thanks.

Hi,
Have never worked with EDI earlier so have some basic questions.
We have an interface for incoming payments. The idea is that the incoming EDI IDOC interface would clear the open items in the customer account.
Initially, have planned to use PEXR200/ REMADV, but realised that it is for creation of a payment advice. Can i use this to clear post and accounting doc or clear an open item in the customer account.
Is there any other IDOC that i can use.
thanks in advance

EDI 823 inbound lockbox

Hello all,
I am using idoc_input_lockbox fm to process finsta01 idocs generated based on EDI 823 format. I am having a custom field in AVIK, payment advice header table which needs to be populated with the 3 fields from the idoc concatenated. Is EXIT_SAPLIEDP_202 right place to do this? I am moving the fields I need from the corresponding segments into the custom field of AVIK and updating idoc_avik parameter with this.

No Response.

FINSTA01 idoc in EDI

Hi All,
Presently im working on edi, Are there any mappings available for <b>EDI 823 file</b> format to <b>FINSTA01 IDOC ?</b> in EDI
I hope you would have somehow managed to get the mapping file. if u have any related stuff ie: edi823 file to incoming edi ( finsta01 idoc in SAP ). Please send me to
Email [email protected]
Thanks in Advance,
Nirupama reddy

Nirupama,
Are you able to get the mappings for X12 to FINSTA01. If u did, can you help me with that. my email: [email protected]
Manohar,
The link you gave does not work.
Thanks,
Gopi

EDI 823 for Lockbox

Hi,
We are trying to implement Lockbox functionality using EDI(FINSTA01 IDOC Type / Lockbx message type).
Where can I find what information will be available in which data segment of the FINSTA01 type?
I went to we60 and there is no detailed information available there.
When we used BAI2, there were lot of materials available online describing what record is for what purpose.
Could anyone guide me in understanding the Segment details?
Thanks,
Ajith Cheruvally

No Response.

Sending the enhanced Infotype 0002 outside SAP via an IDOC

Hello Friends,
We have added couple of Z fields to the standard 0002 Iinfotype table PA0002.
I can see the custom fields in the trans : PA30 screen for infotype 002.
Now, we want to send these custom fields value outside SAP via an IDOC.
Here are the steps I followed :
I created a Z Segment in an extended idoc with the structure PA0002.
I went in transaction PM01 for Infotype 0002 and added the above created Z segment as a 2nd IDOC segment.
In transaction PA30 for 002, I made changes to the custom field value for a person 12039.
Created an idoc via BD21.
IDOC generated with the Z Segment but it doesn't contain any Z custom fields.
Which step am I missing here? Do I have to have a user-exit or BADI to achieve this OR can it be done without writing any code?
Basically I
I will really appreciate your help.
Regards,
Pooja Pandey

Pooja,
you need to fill each field manually.
check this code i am filling ZHCMS_PI_SEMENT
data: sgmnt_e1pityp type e1pityp.
field-symbols: <wplog> type any.
field-symbols: <wplog1> type any.
data: ixxxx type e1pityp, iyyyy type e1plogi,sgmnt_hcms_pi type zhcms_pi_segment,wa_idoc_data_x type edidd, ls_idoc_data type edidd.
data: lv_p0001 type standard table of p0001 ,lv_p0002 type standard table of p0002 ,lv_p0007 type standard table of p0007 .
data: lv_p0521 type standard table of p0521 ,lv_p0710 type standard table of p0710 ,lv_p2001 type standard table of p2001 .
data: ls_p0001 type p0001,ls_p0002 type p0002,ls_p0007 type p0007 ,ls_p0521 type p0521 ,ls_p0710 type p0710 ,ls_p2001 type p2001 .
data: row_index type sy-tabix,del_index type sy-tabix.
data: lcx_root type ref to cx_root.
fILL THE E1PITYP
try.
Keep the segments which have changed date greater than last run date in update mode
    read table idoc_data into wa_idoc_data_x with key segnam = 'E1PITYP'.
    assign wa_idoc_data_x-sdata to <wplog> casting type e1pityp.
    ixxxx = <wplog>.
    loop at idoc_data into wa_idoc_data_x where segnam = 'E1PLOGI'.
      row_index = sy-tabix + 1.
      assign wa_idoc_data_x-sdata to <wplog1> casting type e1plogi.
      iyyyy = <wplog1>.
      sgmnt_e1pityp-plvar = ixxxx-plvar.
      sgmnt_e1pityp-otype = ixxxx-otype.
      sgmnt_e1pityp-objid = iyyyy-objid.
      sgmnt_e1pityp-infty = '0001'.
      sgmnt_e1pityp-begda = ixxxx-begda.
      sgmnt_e1pityp-endda = ixxxx-endda.
      clear ls_idoc_data.
      ls_idoc_data-segnam = 'E1PITYP'.
      ls_idoc_data-sdata = sgmnt_e1pityp.
      insert ls_idoc_data into idoc_data index row_index.
APPEND t_idoc_data .
Get the ZZSWISSREID
      sort lv_p0001 by begda descending.
      read table lv_p0001 into ls_p0001 index 1.
      sgmnt_hcms_pi-zzswissreid = ls_p0001-zzswissreid.
Get the custom data from IT0002
      sort lv_p0002 by begda descending.
      read table lv_p0002 into ls_p0002 index 1.
      sgmnt_hcms_pi-zzglobalid = ls_p0002-zzglobalid.
      sgmnt_hcms_pi-zzsource_id = ls_p0002-zzsource_id.
      sgmnt_hcms_pi-zzlegacy_emp_id = ls_p0002-zzlegacy_emp_id.
      ls_idoc_data-segnam = 'ZHCMS_PI_SEGMENT' .
      ls_idoc_data-sdata = sgmnt_hcms_pi.
      row_index = row_index + 1.
      insert ls_idoc_data into idoc_data[] index row_index.
      clear : lv_p2001[] , lv_p0001[] , lv_p0002[] , lv_p0710[] ,lv_p0007[], lv_p0521[], ls_p2001 , ls_p0001 , ls_p0002 , ls_p0710 ,ls_p0007, ls_p0521 .
APPEND t_idoc_data.
    endloop.
Thanks
Bala Duvvuri

AES filing error - Idoc Outbound Processing: EDI number cannot be compiled

Hi Gurus,
We are configuring the AES filing.
we've done the EDI configI and initally we got the error that EDI partner is not maintained. As per the suggestions from this Forum we've added the cusoms office details in geography tab.
Now when we are trying to process the same, we are getting the error "Idoc Outbound Processing: EDI number cannot be compiled"
All suggestions are welcome.........
Thanks in Advance.

Hi Shiva,
Here goes the solution: you need to maintain the Number of the Number Ranges starting with "10" and this applies only to GTS system as this is HARD-CODED in the Program, apart from 10 any number of the number range will result in an "EDI Number Range compilation" error.
Cheers
Harsha

Need SAP not to clear off the payment in LockBox processing

HI,
In the case of the lockbox processing, we want that the system doews not clear off the invoice in case there is payment difference.
We want to take dicision on those payments manually.
Regards,
MCA

Hi,
You need to define the tolerances in OBA3 and OBXL.
Then the system will not clear off the invoices, instead it will post the ament on account, which you need to then post process.
Regards,
Gaurav

EDI 823 (Inbound) - Field Mapping

Hello,
I need to configure Incoming IDOC EDI 823 for Lockbox.
Basic type: FINSTA01
Message Type: FINSTA
Processing code: FINS
Function Module: IDOC_INPUT_FINSTA
By giving the Basic type u2013 FINSTA01 and executed in the test tool, I am getting the list of all the segments related to this Idoc type.
I request please let me know how I can map the field segments by taking minimum segments and what qualifiers should I input to process the idoc.
Thanks for your co-operation.

No Response.

Lockbox BAI2 - EDI 820 Payment Advice

Hello All,
Thanks very much for your time.
We currently have lockbox with BAI2 format file coming in from the bank for all our customers.
As an enhancement, we want to implement lockbox payment advice to come directly from the customer through EDI 820 payment advice and will only receive the payment header (the 6 record) on the lockbox file from the bank.
The small customers will still follow the current process - send their check and payment advice to the bank and the detail will be transmitted via the BAI2 lockbox file.
I know this can be done - but have some questions regarding the timing of the files and the set up process.
When the EDI 820 payment advice file comes in first, the system can be set up to wait for the header file from the bank to clear the customer account / open items. But if the lockbox file gets in the system before the EDI 820 payment advice file, the payment will get posted on account based on the MICR number without any customization process. Is there a process that has been successfully implemented to deal this scenario?
Please let me know and thanks again for your help.
AM

Incoming payment advice or outgoing? I don't have the details with me, but roughly, you will have to work with the ABAP and EDI people to convert the EDI into the relevant IDOCS (I think the IDOC type is PEXR2002 and msg type is PAYEXT). For automatic postings for incoming EDI/IDOC payment advices the FI consultant will then define the posting rules to the relevant G/L accounts (TCode OT83).
Thanks,
Frank

SAP Lockbox Processing (EDI 823) via FINSTA01 IDoc

Similar Messages

Maybe you are looking for