Lockbox Testing.

Hello Friends,
I have a question in Lockbox testing. I am using BAI2 format for lockbox file. I have done all control and data settings to run FLB2. I was unable to clear the customer invoices when the T.code FLB2 is executed. Both the Cash deposit clearing a/c and Bank Clearing a/c for Lockbox are working fine, in the sense that cash deposit a/c gets debit entry and bank clearing a/c gets credit entry inititally and bank clearing a/c gets debit entry for all the customers that are found due and the customers are posted with credit entry. The customer a/c shows both the credit and debit entry but they are not getting cleared automatically. Am I missing any config step.
Any help is appreciated and rewarded.
Regards,
Sriram

Hi Sriram,
I am having the same problem.. exactly. Did you find a solution? The invoices are getting cleared, the amounts are in the right accounts, but the lockbox clearing account is not getting cleared automatically. I would be highly grateful if you could share your solution.
Regards,
Avi

Similar Messages

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

AR Lockbox interface with BANKS

Hi,
I am given a new task today, to implement / setup lockbox.
My boss told me its just simple as loading to AR interface tables. like sqlloader which has control files .ctl
Can you give me links of docs or Metalink notes on How to setup lockbox?
Thanks a lot

Hi,
Refer to the following links/notes, it should be helpful.
Oracle Receivables Implementation Guide
http://download.oracle.com/docs/cd/B40089_09/current/acrobat/120arig.pdf
Note: 219854.1 - Oracle Receivables Lockbox Troubleshooting Guide
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=219854.1
Note: 177685.1 - Overview of Lockbox
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=177685.1
Note: 133259.1 - Lockbox Troubleshooting Guide
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=133259.1
Note: 107620.1 - How Do You Setup a Lockbox Test?
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=107620.1
Regards,
Hussein

Lock Box file format

Hi All,
I need help on lock box upload file format.I created a test file using bank layout & FLB* structure tables and put a test data for a customer.and tried to process it in FLB2 using pc upload but system didnt select the customer open items.
The file contains details for Record type 1,2,4,5,6,7,8,9.and I dont know what else need to do ,could anyone please provide any guidance on file format?.Thanks
100YPCCDESTINYPCCORIGIN1106221714
2YPCCDESTINYPCCORIGIN000000000040008000801
50010001234567110622YPCCDESTINYPCCORIGIN
6001001000012614407100001300091524660000055555
400100160195590023784
700100012345671106220010000126144
8000000123456711062200010000126144
9000000
thats the file I created but not working.
Regards
Shaun

Hi,
Please refer this links:
how to create Lockbox test file?
http://wiki.sdn.sap.com/wiki/display/ERPFI/ConceptofLockbox
Regards,
Pramitha.

Lockbox Sample test --- posting errors

Hi all !
I am running a sample test file for Locbox process and everythign is working fine as its saying customer uniquely identifies by micr number ... but I am getting all of the items as unprocessed and the error message is saying the following for all the items( I am using four checks in my test file and ts showing same message for all the four)
GL posting error (00 298): Formating error in the field COBL- PRCTR
AR posting error(00 298): Formating error in the field COBL- PRCTR
Algortihm 001 error(00 298): Formating error in the field COBL- PRCTR
Could somone throw somelight on this as I need to do this test config urgently.
Thanks
Regards

Hi,
Please check the field status group of the Clearing account. Is the Profit Center field mandatory for the GL Account?
Thanks
Murali.

Error while testing

hi everybody,
plz help me to solve this problem
when i tried to test the following code i am getting error like
<b>'open_form missing and write_form invalid'</b>
i tried all the ways i know but not able to solve the problem.
      Tables (RFKORI00)
TABLES:   T049L,             "Lockboxes at our House Banks
          VBPA,              "Sales Document: Partner
          RFPOSXEXT,         "## AUTOMATICALLY GENERATED. DO NOT CHANGE OR RE-USE ! ##
          VBRP,              "Billing Document: Item Data
          TVAUT.             "Sales Documents: Order Reasons: Texts
      TYPES
TYPES: BEGIN OF TY_FINALTAB ,
       KUNNR TYPE KNA1-KUNNR,
       NAME1 TYPE KNA1-NAME1,
       BLART TYPE BSID-BLART,
       BELNR TYPE BSID-BELNR,
       BLDAT TYPE BSID-BLDAT,
       WRBTR TYPE BSID-WRBTR,
       FAEDT TYPE RFPOSXEXT-FAEDT,
       REBZG TYPE BSID-REBZG,
       XBLNR TYPE BSID-XBLNR,
       AUGRU TYPE TVAUT-AUGRU,
       RSTGR TYPE BSID-RSTGR,
END OF TY_FINALTAB.
TYPES: BEGIN OF TY_BSID ,
       BUKRS TYPE BSID-BUKRS,
       KUNNR TYPE BSID-KUNNR,
       BSCHL TYPE BSID-BSCHL,
       UMSKZ TYPE BSID-UMSKZ,
       BLART TYPE BSID-BLART,
       BELNR TYPE BSID-BELNR,
       BLDAT TYPE BSID-BLDAT,
       REBZG TYPE BSID-REBZG,
       XBLNR TYPE BSID-XBLNR,
       RSTGR TYPE BSID-RSTGR,
       SHKZG TYPE BSID-SHKZG,
       WRBTR TYPE BSID-WRBTR,
       END OF TY_BSID.
TYPES: BEGIN OF TY_TVAUT,
       AUGRU TYPE TVAUT-AUGRU,
       END OF TY_TVAUT.
      Internal Tables (RFKORI00)
DATA: GT_FINALTAB TYPE TY_FINALTAB OCCURS 0.
DATA: GT_BSID TYPE TY_BSID OCCURS 0.
DATA: GT_TVAUT TYPE TY_TVAUT OCCURS 0.
DATA: BEGIN OF GT_NAME1 OCCURS 0,
      NAME1 LIKE KNA1-NAME1,
      KUNNR LIKE KNA1-KUNNR,
      END OF GT_NAME1.
      Work Areas (RFKORI00)
DATA: BEGIN OF WA_KNA1,
      NAME1 LIKE KNA1-NAME1,
      STRAS LIKE KNA1-STRAS,
      ORT01 LIKE KNA1-ORT01,
      PSTLZ LIKE KNA1-PSTLZ,
      REGIO LIKE KNA1-REGIO,
      LAND1 LIKE KNA1-LAND1,
      END OF WA_KNA1.
DATA: BEGIN OF WA_BSEG1,
      VBELN LIKE BSEG-VBELN,
      KUNNR LIKE BSEG-KUNNR,
      END OF WA_BSEG1.
DATA: BEGIN OF WA_BSID,
       BUKRS TYPE BSID-BUKRS,
       KUNNR TYPE BSID-KUNNR,
       BSCHL TYPE BSID-BSCHL,
       UMSKZ TYPE BSID-UMSKZ,
       BLART TYPE BSID-BLART,
       BELNR TYPE BSID-BELNR,
       BLDAT TYPE BSID-BLDAT,
       REBZG TYPE BSID-REBZG,
       XBLNR TYPE BSID-XBLNR,
       RSTGR TYPE BSID-RSTGR,
       SHKZG TYPE BSID-SHKZG,
       WRBTR TYPE BSID-WRBTR,
      END OF WA_BSID.
DATA: WA_FINALTAB TYPE TY_FINALTAB.
DATA: WA_TVAUT TYPE TY_TVAUT.
DATA: BEGIN OF WA_ADRC,
      ADDRNUMBER LIKE ADRC-ADDRNUMBER,
      TITLE      LIKE ADRC-TITLE,
      NAME1      LIKE ADRC-NAME1,
      STREET     LIKE ADRC-STREET,
      CITY1      LIKE ADRC-CITY1,
      COUNTRY    LIKE ADRC-COUNTRY,
      REGION      LIKE ADRC-REGION,
      END OF WA_ADRC.
DATA:BEGIN OF WA_NAME1,
     NAME1 LIKE KNA1-NAME1,
     KUNNR LIKE KNA1-KUNNR,
     END OF WA_NAME1.
      Global Variables (RFKORI00)
DATA: G_ADRNR1 LIKE T049L-ADRNR.
DATA: G_LOCKB LIKE KNB1-LOCKB.
DATA: G_VBELN LIKE VBPA-VBELN.
DATA: G_AUGRU LIKE TVAUT-AUGRU.
DATA: G_AUGRU_AUFT LIKE VBRP-AUGRU_AUFT.
DATA: G_NAME1 LIKE KNA1-NAME1.
FORM RETRIVE_CUSTDET.
for customer address
SELECT SINGLE NAME1
                 STRAS
                 ORT01
                 PSTLZ
                 REGIO
                 LAND1
                 FROM KNA1
                 INTO WA_KNA1
                 WHERE KUNNR = SAVE_KUNNR.
CALL FUNCTION 'WRITE_FORM'
    EXPORTING
      ELEMENT = 'CUST_ADDRESS'
      FUNCTION = 'SET'
      TYPE     = 'BODY'
      WINDOW   = 'ADDRESS'.
*TO RETRIVE THE VALUES FROM BSID
SELECT SINGLE BUKRS
                KUNNR
                BSCHL
                UMSKZ
                BLART
                BELNR
                BLDAT
                WRBTR
                BSCHL
                SHKZG
                REBZG
                XBLNR
                RSTGR
                INTO WA_BSID
                FROM BSID
                WHERE BUKRS IN UBUKRS
                AND   KUNNR = SAVE_KUNNR
                AND   BSCHL IN HBSCHL
                AND   UMSKZ IN HUMSKZ.
SELECT SINGLE LOCKB
                FROM KNB1
                INTO G_LOCKB
                WHERE BUKRS = WA_BSID-BUKRS.
IF WA_BSID-BUKRS EQ '1100' OR WA_BSID-BUKRS EQ '7100'.
    SELECT SINGLE ADRNR
                  FROM T049L
                  INTO G_ADRNR1
                  WHERE BUKRS = WA_BSID-BUKRS
                  AND LOCKB   = G_LOCKB.
ENDIF.
FOR REMITT ADDRESS
IF G_ADRNR1 IS NOT INITIAL.
    SELECT SINGLE   ADDRNUMBER
                    TITLE
                    NAME1
                    STREET
                    CITY1
                    COUNTRY
                    REGION
                    FROM ADRC
                    INTO WA_ADRC
                    WHERE ADDRNUMBER = G_ADRNR1.
ENDIF.
CALL FUNCTION 'WRITE_FORM'
    EXPORTING
      ELEMENT = 'REMIT_ADDRESS'
      FUNCTION = 'SET'
      TYPE     = 'BODY'
      WINDOW   = 'ADDRESS3'.
*FOR DISPLAYING LINE ITEMS
*for ship-to number
SELECT SINGLE VBELN
                FROM VBPA
                INTO G_VBELN
                WHERE PARVW = 'WE'.
SELECT SINGLE KUNNR
                FROM BSEG
                INTO WA_BSEG1
                WHERE BUKRS = SAVE_BUKRS
                AND   BELNR = SAVE_BELNR
                AND   GJAHR = SAVE_GJAHR
                AND   BUZEI = SAVE_BUZEI.
SELECT SINGLE NAME1
                FROM KNA1
                INTO GT_NAME1
                WHERE KUNNR = WA_BSEG1-KUNNR.
*for Detail document amount
*Fill one range with required posting keys.
RANGES: R_BSCHL FOR BSID-BSCHL.
R_BSCHL-SIGN = 'I'.
R_BSCHL-OPTION = 'BT'.
R_BSCHL-LOW = '01'.
R_BSCHL-HIGH = '09'.
APPEND R_BSCHL.
LOOP AT GT_BSID INTO WA_BSID.
    IF WA_BSID-SHKZG = 'H'.
      WA_BSID-WRBTR = WA_BSID-WRBTR * -1.
      MODIFY GT_BSID INDEX SY-TABIX FROM WA_BSID.
    ENDIF.
ENDLOOP.
*shift -ve sighn to front of amont using fm
CALL FUNCTION 'CLOI_PUT_SIGN_IN_FRONT'
    CHANGING
      VALUE = WA_BSID-WRBTR.
*For retrival of Order Reason
SELECT SINGLE AUGRU_AUFT
                INTO G_AUGRU_AUFT
                FROM VBRP
                WHERE VBELN = G_VBELN.
SELECT SINGLE AUGRU
                INTO WA_TVAUT
                FROM TVAUT
                WHERE AUGRU = G_AUGRU_AUFT
                AND   SPRAS = SY-LANGU.
CALL FUNCTION 'WRITE_FORM'
    EXPORTING
      ELEMENT = 'LINE_ITEMS'
      FUNCTION = 'SET'
      TYPE     = 'BODY'
      WINDOW   = 'MAIN'.
LOOP AT GT_BSID INTO WA_BSID.
    READ TABLE GT_TVAUT INTO WA_TVAUT WITH KEY AUGRU = G_AUGRU_AUFT.
    READ TABLE GT_NAME1 INTO WA_NAME1 WITH KEY KUNNR = SAVE_KUNNR.
    IF SY-SUBRC LT 4.
      MOVE: WA_BSEG1-KUNNR      TO WA_FINALTAB-KUNNR,
             G_NAME1             TO WA_FINALTAB-NAME1,
             WA_BSID-BLART       TO WA_FINALTAB-BLART,
             WA_BSID-BELNR       TO WA_FINALTAB-BELNR,
             WA_BSID-BLDAT       TO WA_FINALTAB-BLDAT,
             WA_BSID-WRBTR       TO WA_FINALTAB-WRBTR,
             SAVE_FAEDT          TO WA_FINALTAB-FAEDT,
             WA_BSID-REBZG       TO WA_FINALTAB-REBZG,
             WA_BSID-XBLNR       TO WA_FINALTAB-XBLNR,
             WA_TVAUT-AUGRU      TO WA_FINALTAB-AUGRU,
             WA_BSID-RSTGR       TO WA_FINALTAB-RSTGR.
      APPEND WA_FINALTAB TO GT_FINALTAB.
      CLEAR GT_FINALTAB.
    ENDIF.
ENDLOOP.
ENDFORM.                    "RETRIVE_CUSTDET
thanx,
hridhayanjili.

Hi hridhyanjili,
1. While using WRITE_FORM,
   we give the ELEMENT NAME
2. That element name
   should be present in the sapscript layout
eg.
/E MYELEMENT
(other wise it will give error)
3. Moreover it should be present in the same window,
   as specified in WRITE_FORM.
regards,
amit m.

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

Lockbox Issue

Hello Experts,
I have a question regarding the lockbox. We are using partial payment option in lockbox (OB10) and we have 0 tolerance at both customer and user level.
The customer has an open invoice of $300 and that he pays $400 towards this invoice.
When I tested this scenario,
a) I got the check status as applied and
b) The Invoice and the payment document are still open.
Is this correct?
My guessing for the check status applied is because of 0 tolerances, lockbox applied the cash to that invoice. If we had any tolerances then overpayment beyond the overpay tolerance amount is not allowed and that the amount sits on the account.
Coming to the point b, because the customer is overpaying the invoice (not exact invoice amount) the invoice is still open. Am I correct?
Please let me know as this is really important.
Regards,
Harish R

this is correct, you will have to manually credit the customer account the $100 for the overpayment.

Payment Advice does not exist- Lockbox Postprocessing

SAP Guru's-
I am unable to double click on the item to view the detail of postprocessing. I thought that by checking the box in config under control parameters it fixed this problem. I am in the test environment and I am unable to view the document under FLB1.
Please help.
Points guaranteed

Hi,
The problem is definitely not related to check box - partially apply.
I think there is some problem in the test file. Are you executing in foreground / background. Once the Lockbox file is executed, are you able to see on the screen if executed in foreground. If executed in background you can check the log.
Also check whether the origin and destination are entered exactly like in configuration in Test file. I suggest just take one line item in the test file and check whther that is getting processed.
Let me know if you are still having an issue in processing the Lockbox file.
Thanks
Murali.

LockBox - Not able to clear customer invoice with partial payment

Importing LB data using FBL2. I can successfully clear full payment. I have tolerance group null for customer setup as below. When I try even a few cents below full invoice amount it posts, but doesn't clear. The account for Over/Underpayments and Unallowed Deductions is setup also below. I can successfully post from fbl5n after importing from lockbox, so I know its my lockbox import setup that's missing something. What am I missing?
          Amount     Percent    Adjust Discount By
Loss 25.00        2.0 %
Chart of Accounts    3000
G/L Account          440000
Short Text           Unallowed Deductions

Are you able to solve this issue. I have the same issue where user wants to clear the few cents automatically and I did the reason codes and assigned an GL account and tested but no luck. Could you please let me know the solution if you got any?
Thank you,
-Harter

Lockbox G/L Journal 1

We are in ECC 6.0 with New GL Activated.
We are implementing the lockbox process, BAI2 format, and we have completed the test fase in Quality and transported to production.
When the user processed the first two files in production, he didn't get the Cash Journal:
Debit = G/L Bank Account
Credit = A/R Clearing Account
The system create (as expected) the journals for AR Application:
Debit = A/R Clearing Account
Credit = A/R
We executed the transaction FLB2 with the following parameters:
Procedure = lockbox
Input record format = BAI2
Invoice numbers = 3
Enhanced Invoice No Check = selected
Algthm: checks with advice = 001
The user executed the same file in Quality and everything worked properly.
We have compared configration and security but we cannot find the reason of the problem.
Do you have any idea what should I check to find the reason of the problem and fix it?
Thank you very much!
Rafael
We have found the problem:
We have a validation rule to check for line item text for documents posted using FB50, FV50, FBVB, FBS1 and FB01 (FB01 to catch the transactions without text from F-02).
When the postings are done throu lockbox import (FLB2) it uses FB01 to do posting in the posting area 1 (Dr Bank/Cr Ar Clearing), the transaction errors out as we do not pass the text in the lockbox input file.
Algthm: checks without advice = 001.
Solution:
Eliminate FB01 from the validation rule.
Edited by: Rafael Bermudez on May 13, 2008 11:56 PM

Modify Validation rule in FI

Lockbox error while posting customer payments

Hello,
I am testing the lockbox file upload and the system was able to locate the Customer number but while clearing customer, I am getting an error saying
No payment advices were found
Message no. F5664
I am trying to edit payment advice and I am getting the error as below
Payment advice 01 10000000 does not exist for account 110006 C850
Message no. FA006
Please let me know why this error is coming.
Thank You.
Edited by: Raghavaa on Dec 26, 2011 8:17 PM

I have found the cause and solution to this problem.
This error ”Fill all required fields SAPMF02D 0111 ADDR1_DATA-NAME1” and other similar errors like “Fill all required fields SAPMF02D 0111 ADDR1_DATA-SORT1“ which occurrs during the IDOC posting when there are more than one sales area or company code occurs when the customer number range is set up for Internal numbering. This means, that the number gets generated only at the time of save and upon debugging the IDOC, we found out that after creating the customer and the first sales area/company code record, the segment E1KNA1M is cleared completely! This is the reason, it throws an error which points to a mandatory KNA1 field as missing. (Like NAME1, SORT1 etc.)
This was resolved by splitting the IDOC into 2.
The solution is to First post only the KNA1 segment and create the customer.
In the second step, pass the IDOC with all other segments along with E1KNA1M, but pass only KUNNR in E1KNA1M and the rest of the fields in E1KNA1M as “/”: you would have got the KUNNR after the first step.
Important note: This requirement to split the IDOCs does not occur when the customer number is known upfront. (Meaning cases where the customer number is externally generated) I also tested this and created a customer with external numbering and I was able to post more than 1 sales area with the same IDOC.
I noticed multiple threads with the same issue, but none of it had a concrete answer. I hope this information will be useful for anyone facing similar problems.
Cheers
Venkat

Lock box config and process to test with test files

hi gurus,
can anyone help me in providing documentation and test file( BAI fomat) totest the functionality.
My client wants to delevelop this functionality.
thanks in advance..
regds,
ram

hi
Lockboxes are a procedure used mainly in the USA to enable checks to be deposited more quickly. The checks the bank sends to you are entered as credits by the bank, and the information entered is sent to the payee using File Transfer. The lockbox files must be formatted per the BAI standard format.
Under certain circumstances, the bank transmits a data carrier to the payee several times a day; the carrier bears the important check information.
From this data carrier, postings are then generated for accounts receivable and G/L accounting.
Lockbox service has the following advantages for the payee:
Better liquidity, thanks to faster collection, depositing, and crediting of checks
Reduced processing workload
Procedure
To import lockbox data, proceed as follows:
Choose Incomings ® Lockbox ® Import.
You reach the initial screen.
Specify the path and file name of the lockbox file.
Specify the import options.
Choose Program ® Execute.
===========================================================
From the SAP Easy Access Screen select Accounting ® Treasury ® Cash Management ® Incomings ® Lockbox ® Postprocess or Accounting ® Banking ® Incomings ® Lockbox ® Postprocess.
2. Enter the required data and choose Execute.
The selected lockbox data is displayed in a hierarchy. The icons in front of each line show the status of the check. The following are possible status entries:
¡ Posted
¡ Posted on account
¡ Partially applied
¡ Not posted
Proceed as follows to display the check status:
a. Choose View ® Other Display
The screen for displaying lists appears.
b. Click on the ALV icon Layout settings and choose Change layout.
c. Select the Check Status field in the dialog window under Column List.
d. If you want to use the field in the column list, click on the left arrow and choose Copy.
The system displays the check status.
3. Edit Payment Advice
¡ In order to edit the payment advice, double-click on the Payment Advice field in the list display. Change the data you want to correct, save and choose Back.
¡ If you want to change the account or account type, show the Account and Account Type fields as described for the Check Status field. Both fields are shown in the list display and you can change them directly. Choose Enter to save the changed data.
If you want to ensure that your changes have been saved, double-click on the Payment Advice field and choose Payment Advice ® Header.
4. Choose Checks ® Post to resume the automatic posting of changed checks.
Hope this helps. please assign points.

Lock Box Issue - Test Program RFEBLBT2

I am trying to create some test data for my lockbox config. Does anyone know what this program creates? I thought it creates receipts data.
As a pre-requisite I created an invoice via FB70. Then I created some test data via RFEBLBT2 and used t code FLB2 to post this test data saved in a text file.
The information seems to post "ON ACCOUNT" and does not clear the receivable.
Can someone please help me?
thanks so much
Brian

I am trying to create some test data for my lockbox config. Does anyone know what this program creates? I thought it creates receipts data.
As a pre-requisite I created an invoice via FB70. Then I created some test data via RFEBLBT2 and used t code FLB2 to post this test data saved in a text file.
The information seems to post "ON ACCOUNT" and does not clear the receivable.
Can someone please help me?
thanks so much
Brian

About Post Processing transaction FLB1- lockbox details

Hi ALL,
we are doing an upgradation from 4.6 to ECC 6.0 so we have a TST system which is upgraded for unit testing purpose..
now the scenario is....
we have been loading the raw data into idoc files into SAP thru an interface called GXS, so when they are loaded, now in PRD after they see the idocs had been loaded good in we02, they are able to look the lockbox data in FLB1 (as unprocessed) even before processing the import lockbox processing transaction.
but we are not able to see the same lockbox data in FLB1 even when we can see that the idocs are loaded good in the TST system, when we go into the FLB1 transaction it says...
"You have selected either no or several items.
To select, double-click on an item
at the top (list) or on the left (tree display)
of the screen".
i was wondering if we are able to see the lockbox data in PRD (4.6) system, then why are we not able to look into the data (lockbox details) in TST (6.0)
but when i ran the import program FLBP in TST and then when i check the FLB1 transaction it shows the details now ..i.e., on account , unprocessed n so on..
but the user wants to see the lockbox data in FLB1 as unprocessed even before running FLBP
i am not able to understand what could be the issue with this...please advice me ....thanks in advance

Hi,
If you are looking to view the specific fields on the screen without scrolling then , you can set up a line layout in configuration and attach it to transaction code FB05 for Customers.
The transaction codes for defining line layout and attaching the line layout to Transaction code are as O7Z4S and O7V3.
Thanks
Murali.

Lockbox Testing.

Similar Messages

Maybe you are looking for