Difference occurs after PCA Transferred for Accounts Receivable

Hi All,
There is a ticket which says.."Difference occurs after PCA Transferred for Accounts Receivable in month end ".
Can anyone help me in understanding the concept. What exactly does it mean and where do i need to check.
Thanks
Mercy

We were able to trace the reason for the difference.
We checked the difference between FI and PCA and found it is due to old document clearing timing problem.
Since it happened in April and we cannot change in FI , we can only manually adjust in PCA itself.
Thanks,
Mercy

Similar Messages

Tutor Material for Account Receivable

Please help with Tutor Material ( study material) for account Receivable. I preparing to study this module but i do not have a study material. If someone has this material or know were i can download please share.

Hi,
It depends what type of information you are after. You can download the Oracle E-Business suite documentation CD from Metalink (or view the library online). In there you will find the Receivables User Guide, Tax manual and API reference guides amongst others (eg. Vertex Integration Guide).
Outside of the standard product docs, there are several books out there, such as the Financials Handbook (McGraw-Hill) that contain good sources of information for the core financials modules.

BAPI / LSMW for Accounts Receivable open items and G/L Accounts balance

I want to transport legacy data to SAP.
Please provide me with a BAPI or LSMW for creating entries for
Accounts Receivable open items
General Ledger Accounts balances

Thomas,
Program RFBIBL00 is traditionally used for converting FI transactions. In LSMW, it's object 0100, sub object 0000.
-nathan

Table for accounts receivable

Hi experts,
Which table stores accounts receivable and accounts payable data mainly?
prasad

Dear,
It all depends upon what kind of data you look at, because if you want to know the data pertains to masters or transactions for account receivable and accounts payable.
Master data tables:
Vendor Master : LFA1, LFB1, LFBK, LFBW,ADRC, LFC1 etc
Customer Master : KNA1, KNB1, KNBK, KNC1etc.
Transaction data:
Customer
BSID - Customer Open Items
BSAD- Customer cleared items.
Vendor
BSIK - Vendor Open Items
BSAK- Vendor cleared items.

Cheque process for Accounts receivable

Hi,
Can anyone please provide me some documents/links to documents which give the entire process for:
1 - Confiurations required for using cheques for accounts receivable
2 - Configurations required for Post Dated Cheques
3 - Business process in SAP for cheques i.e posting,clearing and tables in which data is stored.
Thanks in advance.
Regards,
Ajit

Hi,
There is a lot of documentation available on the internet , as well you can check help.sap.com. Many books relavant to the configuration, you will get on the internet.
Regards,
Van

Looking for Account Receivable, Account payable info cube

i m looking for Account Receivable, Account payable info cube in business contnet.
i search a lot on help.sap.com but could not find them.

Hi,
Please check the link below for AP and AR business ontent:
http://help.sap.com/saphelp_nw2004s/helpdata/en/ee/cd143c5db89b00e10000000a114084/frameset.htm
Thanks and Regards
Subray Hegde

Which custom. steps for "Accounts Receivable Pledging Indicator" (KNB1)?

Hi All,
Could anyone show me the customizing steps to set the "Accounts Receivable Pledging Indicator" (KNB1-CESSION_KZ)?
Thanks
Galdalf

Hi ,
Pledging indicator is basically used in the Accounts Receivable Factoring Process. Factoring is the process of the transfer of a receivable from the previous creditor (assignor) to a new creditor (assignee).
The Menu Path for creating the Pledging indicator is as below:
Financial Accounting > Accouts Receivable and Accounts Payable> Customer Account > Master Data > Preperation for creating master data > Define Accounts Receivable Pledging Indocator
This indicates in the master record that a customer should be involved in the accounts receivable factoring procedure. The indicator is automatically transferred to the line item during posting but can also be entered manually.
Also you can refer to the thread A/R Functionality in SAP for more details of the process.
Hope it helps
SJ
Edited by: Sumit Jain on Jul 7, 2009 1:32 PM

PRA - Process Improvement for Accounts Receivable and Taxes Payable

SAP PRA introduces process improvements to Accounts Receivable and Taxes Payable write off processes for small dollar line items. When small dollar line item amounts are within the user defined tolerances, these line items can be written off using a batch job, Auto Write Off.

Thank you Wolfrad-
It's a good start. I think the best method in creating roles is to create the name myself and add the t-codes pertaining to that function such as cash application and credit.
I have a list of t-codes (it says all FI transactions) but I don't see credit management t-codes like FD32. Does anyone have a list of credit management t-codes?
Thanks!
POINTS AWARDED

Report that display payment terms for account receivables customers

Hello To all,
Please can you help us to find a standard report that list account receivables customers with their payment terms.
Regards.
Zied.

Hello,
Thank you for your response but user has not authorisation to access to SE16 and we need a report to do this.
Or may be we can create a query that use KNB1 table.
Regards.
Zied.

Stored Procedure for Accounts Receivable

Hi. First off, apologies in advance if I have put this question into the wrong topic. Secondly, I first saw SAP 3 weeks ago when I stared my new job and have had no training so please bear with me if some of what I ask doesn't make much sense.
OK, the issue is this. In SAP B1, there is a built in Report called "Customer Receivables Aging" which allows you to see Customer Receivable Accounts by age (e.g 0-30, 31-60, 61-90, 90+) and so on. The problem with the built in report is that it doesn't show all the fields I want - it only shows the Customer Name, balance, and then the aging balances. I want to be able to see things like the customer's contact details, etc. I know this makes no sense because the whole point of the report is to be able to drill down into the different rows, but this report needs to be issued in printed form, hence the need for the extra fields.
Since I can't seen any way from within SAP to change the fields returned by this report, I thought I'd have a stab at writing my own SQL to select out the same data along with the extra fields I wanted. That's when the problems began...try as I might, I cannot get my figures to tally with the SAP Report.
They are almost correct, but not quite. I am sure that I am missing a selection or some other element of the logic that B1 uses to create the built in report.
If you want, I can post the SQL I'm using....I'm not an SQL guru by any means, but I do know my way around it; the biggest problem I have is that I cannot find any documentation as to the 4 letter tables that SAP uses and their relationships except on the most basic level (e.g ORIN is Open Return Invoice [maybe])
Then I thought maybe it might be possible to edit that report section in B1 using the SDK. That would be a better solution as I would not have to 'reinvent the wheel', I can just SELECT an extra field or three to include in the report.
So my question is
->Does anyone have a stored procedure for SQL Server that can replicate correctly the SAP B1 "Customer Receivable Aging", even just the process SAP uses to gather this data would be good.
OR
is it possible to edit this report in SAP to put in the extra fields I want.
Or, am I totally barking up the wrong tree? Thanks in advance, I know this is a long post.

Hi Stephen,
There should be a print layout attached to the on-screen report. This can be altered to show the additional fields you want without resorting to SDK or SQL development.
When you have the Customer Receivables Ageing report open on screen, choose Tools-Print Layout Designer or click on the Print Layout Designer icon on the toolbar. When prompted, choose the layout you wish to edit and you'll be taken to the layout design. In the layout, you can add additional fields and should be able to add most business partner fields. As the report is set to portrait by default, I recommend changing it to landscape so you have lots more space to add the extra fields you want. This report writer is fairly intuitive, if a little basic.
You will need to save this new report design, set it to be the default layout and then when you select to print the Customer Receivables Ageing report (ie Print Preview or Print) you will see the new report.
Hope this helps,
Owen

Retention for Accounts Receivable

Dear Gurus,
We have a requirement to retain some amount paid in each invoice verification for a particular vendor to a separate account and make payment after the completion of the project.
I have been trying to do this using payment terms. I was able to split the invoice amount according to payment terms but the amounts are both for the vendor reconsolation account , but i am unaware how to post a particular percentage to a separate account during invoice verification.
Please Help
Thanks in advance
Regards

hI,
in a simple way you can post to a separae GL account ducring the invoice posting .
You can use the tab GL account in the MIRO item over screen and enter the GL you wish , for the amount and post.For LIV transactions you can refer to below link .
http://help.sap.com/printdocu/core/print46c/en/data/pdf/MMIVLIV/MMIVLIV.pdf
Regards,

F110 for Accounts receivable

Points available.
Is the F110 payment only used for outgoing payments? Can it be used to process incoming payments from customers? If yes, how do we go about setting the config? Is it similar to the config used in FBZP?
Thanks in advance!

Hello Manu,
Thanks for your response. Let me clarify what I mean when I say 'processing' incoming customer payments. Our client has a distributor that sells our product to customers. When customers buy our product thru the distributor, they (customers) have the option of splitting the payments over several months. Every month, the distributor will send a file that has the customers partial payment for that month. Our client in turn interfaces that file to SAP and creates invoices. Every month when the customer sends a partial payment our client needs to post that payment against the invoice. Hope that makes sense.
We think that F-28 can help us post incoming payments. We can put the GL acct, the amount and select document number. You can then hit Process OI and on the next screen enter the invoice # and again process open items. Then on the Partial pmts tab we can enter whatever partial pmt the customer sent.
The problem is this: Once all the pmts for a particular invocie have come in, the invoice still remains in the Process OI screen. Why does it not go away? I know if I execute F-32, I can clear it. But does SAP have a way to automatically clear the invoice?
Thanks in advance!

Accounts Receivable payment schedule

Hello,
Have you ever heard of a payment schedule possibility for Accounts receivable? This payment schedule is different then the scheduled billing. It occurs after the invoices have been posted and the customer is requesting to allow a change in the due dates of his open items. An agreement is then made with the customer that a certain percentage of the items are paid by date N, another by date N+1 etc. Usually this is done when the customers have a cash flow issue and also in cases when a product is just release and this kind of deviations from standard payments are allowed (this is not to be looked as a usual installment payment).
Besides storing the data somewhere in SAP the business is also requesting to be able to see this information in various reports i.e. FBL5 (they need to see the due date according to the payment term and the due date according to the payment schedule), Aging (aging according to the regular payment term and due date, and aging according to the payment schedule).
Thanks a lot!
Cristina

Contract Accounting was available but only on an industry solution.
IS MEDIA
IS UTILITIES
IS INSURANCE
IS PUBLIC SECTOR
if you are not in one of those sectors, you will need to upgrade before you can get access to Contract Accounting.
Switching from FI-AR to CA-AR is a project in itself.

Accounts Receivable Report: Customer Wise Ageing Analysis report -FI module

Hi Gurus,
 Can anyone help me in providing standard report(source code) or already done sample report(source code) for Accounts Receivable Report: Customer Wise Ageing AnalysisThis is in FI Module. Though it is FI Module we need to fetch details related to Sales Module, and the days should be <0 30 60 90 120 180 365 >365
It is urgent I need to deliver this report by this week end.
Please help me . Waiting for your reply.
Points Rewarded for help rendered and I would personally send a good gift if you can help me
Yours Truly,
Rajiv Christopher.
Edited by: Rajiv Christopher on Apr 2, 2008 11:33 AM

Hi,
i am attaching aging report.
see if this is useful to you.
REPORT ZFUS0102 MESSAGE-ID OA
 LINE-SIZE 270.
Title: GR/IR AGING REPORT
Date: January 2001
TABLES: DISVARIANT, EKPO.
TYPE-POOLS: SLIS.
Tables
TABLES:
BSIS,
EKKO.
working table
DATA: BEGIN OF RTAB OCCURS 0,
 HKONT LIKE BSIS-HKONT,
 ZUONR LIKE BSIS-ZUONR,
 BUDAT LIKE BSIS-BUDAT,
 SHKZG LIKE BSIS-SHKZG,
 DMBTR LIKE BSIS-DMBTR,
 PRCTR LIKE BSIS-PRCTR,
 END OF RTAB.
DATA: BEGIN OF WTAB OCCURS 0,
 ZUONR(2) TYPE N,
 PRCTR LIKE BSIS-PRCTR,
 DAYS(4) TYPE P,
 DMBTR LIKE BSIS-DMBTR,
 END OF WTAB.
DATA: BEGIN OF PTAB OCCURS 0,
 ZUONR(2),
 PRCTR LIKE BSIS-PRCTR,
 AMT30 LIKE BSIS-WRBTR,
 AMT60 LIKE BSIS-WRBTR,
 AMTPL LIKE BSIS-WRBTR,
 TOTAL LIKE BSIS-WRBTR,
 END OF PTAB.
PARAMETERS: COMPANY LIKE BSIS-BUKRS OBLIGATORY,
 ACCT LIKE BSIS-HKONT OBLIGATORY,
 DATE LIKE SY-DATUM OBLIGATORY.
SELECT-OPTIONS: S_EKORG FOR EKKO-EKORG.
PARAMETERS: P_VARI LIKE DISVARIANT-REPORT.
DATA: WS-AMT30 LIKE BSIS-WRBTR.
DATA: WS-AMT60 LIKE BSIS-WRBTR.
DATA: WS-AMTPL LIKE BSIS-WRBTR.
DATA: TITLE(21) VALUE 'GR/IR Aging Report'.
DATA: LIN TYPE I.
DATA: GX_VARIANT LIKE DISVARIANT,
 G_VARIANT LIKE DISVARIANT.
DATA: LAYOUT TYPE SLIS_LAYOUT_ALV,
 L_F TYPE SLIS_T_FIELDCAT_ALV WITH HEADER LINE,
 GROUP TYPE SLIS_T_SP_GROUP_ALV WITH HEADER LINE,
 COLOR TYPE SLIS_T_SPECIALCOL_ALV WITH HEADER LINE.
DATA: LT_TOP_OF_PAGE TYPE SLIS_T_LISTHEADER,
 LS_LINE TYPE SLIS_LISTHEADER,
 T_EVENTS TYPE SLIS_T_EVENT.
CONSTANTS: FORMNAME_TOP_OF_PAGE TYPE SLIS_FORMNAME VALUE 'TOP_OF_PAGE'.
INITIALIZATION.
PERFORM EVENTTAB_AUFBAUEN USING T_EVENTS[].
PERFORM VARIANT_INIT.
Get default variant
GX_VARIANT = G_VARIANT.
CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'
 EXPORTING
 I_SAVE = 'A'
 CHANGING
 CS_VARIANT = GX_VARIANT
 EXCEPTIONS
 NOT_FOUND = 2.
IF SY-SUBRC = 0.
 P_VARI = GX_VARIANT-VARIANT.
ENDIF.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_VARI.
PERFORM VARIANT_INPUTHELP_F14.
START-OF-SELECTION.
LS_LINE-TYP = 'S'.
WRITE SY-DATUM TO LS_LINE-INFO DD/MM/YY.
WRITE SY-UZEIT TO LS_LINE-INFO+10.
WRITE SY-UNAME TO LS_LINE-INFO+20.
WRITE TITLE TO LS_LINE-INFO+30.
APPEND LS_LINE TO LT_TOP_OF_PAGE.
PERFORM FIELDS.
IF NOT P_VARI IS INITIAL.
 PERFORM PAI_OF_SELECTION_SCREEN.
ELSE.
 CALL FUNCTION 'REUSE_ALV_VARIANT_SELECT'
 EXPORTING
 I_DIALOG = ' '
 I_USER_SPECIFIC = 'A'
 I_DEFAULT = ' '
 I_TABNAME_HEADER =
 I_TABNAME_ITEM =
 IT_DEFAULT_FIELDCAT = L_F[]
 I_LAYOUT = LAYOUT
 IMPORTING
 E_EXIT =
 ET_FIELDCAT = L_F[]
 ET_SORT =
 ET_FILTER =
 CHANGING
 CS_VARIANT = DISVARIANT
 EXCEPTIONS
 WRONG_INPUT = 1
 FC_NOT_COMPLETE = 2
 NOT_FOUND = 3
 PROGRAM_ERROR = 4
 OTHERS = 5.
ENDIF.
Decide which tables to access.
PERFORM MAIN_SELECT.
MOVE TITLE TO LAYOUT-WINDOW_TITLEBAR.
CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
 EXPORTING
 I_CALLBACK_PROGRAM = 'ZFUS0102'
 I_CALLBACK_USER_COMMAND = 'USER_COMMAND'
 IS_LAYOUT = LAYOUT
 IT_FIELDCAT = L_F[]
 IT_SPECIAL_GROUPS = GROUP[]
 I_SAVE = 'A'
 IS_VARIANT = G_VARIANT
 IT_EVENTS = T_EVENTS
 TABLES
 T_OUTTAB = PTAB
 EXCEPTIONS
 PROGRAM_ERROR = 1
 OTHERS = 2.
 FORM FIELDS *
FORM FIELDS.
L_F-FIELDNAME = 'ZUONR'.
L_F-OUTPUTLEN = 6.
L_F-SELTEXT_L = 'SERIES'.
L_F-REPTEXT_DDIC = 'SERIES'.
L_F-REF_TABNAME = 'PTAB'.
L_F-SP_GROUP = 'A'.
APPEND L_F. CLEAR L_F.
L_F-FIELDNAME = 'PRCTR'.
L_F-OUTPUTLEN = 10.
L_F-SELTEXT_L = 'PROFIT CTR.'.
L_F-REPTEXT_DDIC = 'PROFIT CTR.'.
L_F-REF_TABNAME = 'PTAB'.
L_F-SP_GROUP = 'A'.
APPEND L_F. CLEAR L_F.
L_F-FIELDNAME = 'AMT30'.
L_F-SELTEXT_L = '30 DAYS'.
L_F-REPTEXT_DDIC = '30 DAYS'.
L_F-REF_TABNAME = 'PTAB'.
L_F-SP_GROUP = 'A'.
L_F-REF_TABNAME = 'BSIS'.
L_F-REF_FIELDNAME = 'WRBTR'.
L_F-DO_SUM = 'X'.
APPEND L_F. CLEAR L_F.
L_F-FIELDNAME = 'AMT60'.
L_F-SELTEXT_L = '60 DAYS'.
L_F-REPTEXT_DDIC = '60 DAYS'.
L_F-REF_TABNAME = 'PTAB'.
L_F-SP_GROUP = 'A'.
L_F-REF_TABNAME = 'BSIS'.
L_F-REF_FIELDNAME = 'WRBTR'.
L_F-DO_SUM = 'X'.
APPEND L_F. CLEAR L_F.
L_F-FIELDNAME = 'AMTPL'.
L_F-SELTEXT_L = '60+ DAYS'.
L_F-REPTEXT_DDIC = '60+ DAYS'.
L_F-REF_TABNAME = 'PTAB'.
L_F-SP_GROUP = 'A'.
L_F-REF_TABNAME = 'BSIS'.
L_F-REF_FIELDNAME = 'WRBTR'.
L_F-DO_SUM = 'X'.
APPEND L_F. CLEAR L_F.
L_F-FIELDNAME = 'TOTAL'.
L_F-SELTEXT_L = 'TOTAL'.
L_F-REPTEXT_DDIC = 'TOTAL'.
L_F-REF_TABNAME = 'PTAB'.
L_F-SP_GROUP = 'A'.
L_F-REF_TABNAME = 'BSIS'.
L_F-REF_FIELDNAME = 'WRBTR'.
L_F-DO_SUM = 'X'.
APPEND L_F. CLEAR L_F.
ENDFORM.
 FORM MAIN_SELECT *
FORM MAIN_SELECT.
SELECT HKONT ZUONR BUDAT SHKZG DMBTR PRCTR
 INTO TABLE RTAB
 FROM BSIS
 WHERE BUKRS = COMPANY
 AND HKONT = ACCT.
IF SY-SUBRC = 0.
 SORT RTAB.
 PERFORM PROCESS_RTAB.
 PERFORM PROCESS_WTAB.
ENDIF.
ENDFORM. " MAIN SELECT
 FORM VARIANT_INPUTHELP_F14 *
FORM VARIANT_INPUTHELP_F14.
DATA: G_EXIT(1) TYPE C.
CALL FUNCTION 'REUSE_ALV_VARIANT_F4'
 EXPORTING
 IS_VARIANT = G_VARIANT
 I_SAVE = 'A' " g_save
 it_default_fieldcat =
 IMPORTING
 E_EXIT = G_EXIT
 ES_VARIANT = GX_VARIANT
 EXCEPTIONS
 NOT_FOUND = 2.
IF SY-SUBRC = 2.
 MESSAGE ID SY-MSGID TYPE 'S' NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ELSE.
 IF G_EXIT = SPACE.
 P_VARI = GX_VARIANT-VARIANT.
 ENDIF.
ENDIF.
ENDFORM.
 FORM USER_COMMAND *
--> UCOMM *
--> SELFIELD *
FORM USER_COMMAND USING UCOMM LIKE SY-UCOMM SELFIELD TYPE
SLIS_SELFIELD.
IF UCOMM EQ '&IC1'.
 IF SELFIELD-TABINDEX <= 0.
 MESSAGE S108.
 EXIT.
 ENDIF.
IF SELFIELD-SEL_TAB_FIELD CS 'LIFNR'.
 SET PARAMETER ID 'LIF' FIELD SELFIELD-VALUE.
 CALL TRANSACTION 'XK02'.
ELSE.
 IF SELFIELD-SEL_TAB_FIELD CS 'VEND'.
 SET PARAMETER ID 'LIF' FIELD SELFIELD-VALUE.
 CALL TRANSACTION 'FBL1'.
 ENDIF.
ENDIF.
 CLEAR SY-UCOMM. CLEAR UCOMM.
ENDIF.
ENDFORM.
 FORM TOP_OF_PAGE *
FORM TOP_OF_PAGE.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
 EXPORTING
 IT_LIST_COMMENTARY = LT_TOP_OF_PAGE.
ENDFORM.
 FORM EVENTTAB_AUFBAUEN *
--> P_T_EVENTS *
FORM EVENTTAB_AUFBAUEN USING P_T_EVENTS TYPE SLIS_T_EVENT.
DATA: LS_EVENT TYPE SLIS_ALV_EVENT.
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
 EXPORTING
 I_LIST_TYPE = 0
 IMPORTING
 ET_EVENTS = P_T_EVENTS.
READ TABLE P_T_EVENTS WITH KEY NAME = SLIS_EV_TOP_OF_PAGE
 INTO LS_EVENT.
IF SY-SUBRC = 0.
 MOVE FORMNAME_TOP_OF_PAGE TO LS_EVENT-FORM.
 APPEND LS_EVENT TO P_T_EVENTS.
ENDIF.
ENDFORM. " EVENTTAB_AUFBAUEN
 FORM PAI_OF_SELECTION_SCREEN *
FORM PAI_OF_SELECTION_SCREEN.
IF NOT P_VARI IS INITIAL.
 MOVE G_VARIANT TO GX_VARIANT.
 MOVE P_VARI TO GX_VARIANT-VARIANT.
 CALL FUNCTION 'REUSE_ALV_VARIANT_EXISTENCE'
 EXPORTING
 I_SAVE = 'A' " g_save
 CHANGING
 CS_VARIANT = GX_VARIANT.
 G_VARIANT = GX_VARIANT.
ELSE.
 PERFORM VARIANT_INIT.
ENDIF.
ENDFORM. " PAI_OF_SELECTION_SCREEN
 FORM VARIANT_INIT *
FORM VARIANT_INIT.
CLEAR G_VARIANT.
G_VARIANT-REPORT = 'ZFUS0102'.
ENDFORM. " VARIANT_INIT
*& Form PROCESS_RTAB
 text
--> p1 text
<-- p2 text
FORM PROCESS_RTAB.
DATA TLNS TYPE I.
DESCRIBE TABLE S_EKORG LINES TLNS.
LOOP AT RTAB.
 IF TLNS GT 0.
 SELECT SINGLE EKORG FROM EKKO INTO EKKO-EKORG
 WHERE EBELN = RTAB-ZUONR(10).
 CHECK EKKO-EKORG IN S_EKORG.
 ENDIF.
 IF NOT RTAB-BUDAT > DATE.
 MOVE RTAB-ZUONR(2) TO WTAB-ZUONR.
 COMPUTE WTAB-DAYS = DATE - RTAB-BUDAT.
 IF RTAB-SHKZG = 'H'.
 WTAB-DMBTR = RTAB-DMBTR * -1.
 ELSE.
 WTAB-DMBTR = RTAB-DMBTR * 1.
 ENDIF.
 MOVE RTAB-PRCTR TO WTAB-PRCTR.
 APPEND WTAB.
 ENDIF.
ENDLOOP.
FREE RTAB.
ENDFORM. " PROCESS_RTAB
*& Form PROCESS_WTAB
 text
--> p1 text
<-- p2 text
FORM PROCESS_WTAB.
SORT WTAB BY ZUONR PRCTR DAYS.
LOOP AT WTAB.
 PTAB-ZUONR = WTAB-ZUONR.
 PTAB-PRCTR = WTAB-PRCTR.
 AT END OF DAYS.
 SUM.
 IF WTAB-DAYS > 60.
 WS-AMTPL = WS-AMTPL + WTAB-DMBTR.
 ELSE.
 IF WTAB-DAYS > 30.
 WS-AMT60 = WS-AMT60 + WTAB-DMBTR.
 ELSE.
 WS-AMT30 = WS-AMT30 + WTAB-DMBTR.
 ENDIF.
 ENDIF.
 ENDAT.
 AT END OF PRCTR.
 PTAB-AMTPL = WS-AMTPL.
 PTAB-AMT30 = WS-AMT30.
 PTAB-AMT60 = WS-AMT60.
 COMPUTE PTAB-TOTAL = PTAB-AMTPL + PTAB-AMT30 + PTAB-AMT60.
 APPEND PTAB.
 WS-AMTPL = 0.
 WS-AMT30 = 0.
 WS-AMT60 = 0.
 ENDAT.
ENDLOOP.
SORT PTAB BY ZUONR PRCTR.
ENDFORM. " PROCESS_WTAB
regards,
Sindhu

Account Receivable Factoring/Pledging Process

Hi SAP guru,
We are implementing a Factoring solution in SAP ECC6.0 and would like anyoen of you to share the knowledge around SAP standard solution
- What functionality does Pledging indicator/Procedure do?
- What would be the Business Process?
- How would the system handle the factoring fee?
- If any documentation available, please share with us.
I would appreciate it if you could provide more of your expertise.
taro

In SAP, the term used for Factoring is Pledging.
You have to first activate the Pledging Procedure per Co. Code, by following the path: Financial Accounting Global Settings -> Company Code -> Activate Accounts Receivable Factoring Procedure per Company Code.
After that, navigate to Accounts Receivable and Accounts Payable -> Customer accounts -> Master Records -> Preparations for Creating Customer Master Records -> Define Accounts Receivable Factoring Indicator to define your pledging indicators.
Be sure to read the IMG notes at these nodes. Also, check out this page:
http://community.cimaglobal.com/discussions/information-technology/factoring-using-sap-erp?q=discussions/information-technology/factoring-using-sap-erp#comment-19441
Should be enough to get you started.
Hope this helps.
BR / Gulshan

Difference occurs after PCA Transferred for Accounts Receivable

Similar Messages

Maybe you are looking for