Functional specifications on F-32 residual payment

Hello,
I need Functional specifications on F-32 residual payment. If some one has that then please share it with me.
Thanks and Regards,
Rajesh Kumar Mantri.
Moderator: This is standard core SAP transaction with no 'functional specifications'.

Hi,
What exactly do you need to know about F-32?
When you do residual clearing, it clears the original document and opens a new line item for that customer for the remaining value.

Similar Messages

Terms of Payment in case of Residual Payment

Dear All
I have made a Terms of Payment K1 for my Customer. After making a residual payment, the terms of payment for the residual amount is coming by default 0004. But I want it should come from Original Invoice payment terms...
Please guide me.
Kanwaljit

Hi,
Goto the TCODE : OBA3
in that check the payment terms given in the "Specifications for posting residula item for payment differences" category. Remove the payment term and select the "Payment term from invoice"
VVR

Limiting or control for Residual payment with reason codes

Hi FI Gurus,
When we are received or making payment to customer or vendor, sometimes we need to clear the invoice by receiving or making payments with small differences through residual payment. Is there any control for limiting residual payment.
Lets have an example
invoice posted for 1000
customer dr 1000
sales       cr 1000
Partial payment recd 500
cash/bank dr 500
customer cr   500
final payment received 350 and balanace amount adjusted with residual payment by defining reason code like rounding off difference. So in this case accounting entry will be
customer cr 350
rounding off diff 150
cash/bank 500
being final payment agaisnt invoice
My question:   Is there any way to restrict the residual payment like 10% or 20% of total invoice i.e. 100 or 200 and not more than 20% ? other wise sometime user may adjust any amount may be 100000 through this way by putting the same reason code, which is not fair.
I checked SPRO setting but i did not get anyt setting relating to above case.
If any body know, please let me know? Thanks in advance
Regards,
Prakash

Hi Lawerance,
Thanks for reply.
But I am looking for amount adjusted through residual with reason code. I dont think there is any limitation or control in the SPRO standard setting. Tolerance is preventing user to post document for more than a specific amount. But my question is something different.
I want to control the user for adjusting amount from residual tab with selecting reason code. In other words user should not adjust more than some limit with residual payment by selecting reason codes. Thanks.
Regards,
Prakash

Residual payment should not allow more than Vendor Invoice

Hi,
Eg: Vendor has booked invoice 5000 INR, when user make payment through F-53 or F-58 through "Residual" payment user can pay more than invoice 5002 INR and below accounting entry is posting.
Bank Cr 5002 INR
To Vendor Dr 5000 INR (Invoice amount)
To Vendor Dr 02 INR Excess than invoice
Business requirement is system should not allow pay more than invoice amount. How to control suggestion would be appreciated.
I have done below settings for your understanding here system configuration.
1. OBA3: Under "Permitted Payment difference" zero for Gain , Loss , Amount, Percent & Adjust Discount By However "Permitted Payment Differences for Automatic write-Off(Function code AD)" zero.
2. OBA4: Cash discount per line item: Zero and Under "Permitted Payment difference" Revenues, Expense, Percent & Cash discount put Zero.
Regards,
Babu.

Hi Prashant,
I have restricted many fields to use through screen variant now user can not pay more than Invoice amount except through Residual payment process.
Client side management strongly says that they want to use Partial and Residual payment process options but user should not allow pay more than invoice amount.
If any solution please guide me.
Regards,
Babu.

EXIT_SAPMM06E_016 for User exit how to prepare functional specification.

Hello Gentlemen,
Ex: - issue for the PO no: 4500006789
Made advance payment against PO 100%, later vendor has given discount on freight charges, so once advance payment is made then system should not allow to amending the PO.
Now client requirements are as follows likeu2026.
Condition no1: If there is an existing down payment against the PO then system should allow to amending the PO, but system should throw the warning message as there is already down payment against the PO.
Condition no2: If there is an existing down payment against the PO system should allow to amending the PO, but system should not allow to changing more than the total value of the PO.
So User exit which I have mentioned in above subject line it should be in a position to fullfill the condition no1 and condition no2.
So pleas let me know the functional specification and functional specification logic for above said in subject User exit.
Early action inthis matter will be highly appreciated.

as far as i know, when you make an advance payment you can link it to a po only thru a reference text field.
uncleared vendor items will be table BSIK
you may have to filter it out by transaction type A and spl gl indicator A, both refering to down payment.
this way you can find out what is the advance payment still with the vendor.

Smart Form Functional Specification

Hi Gurus,
I have to design a smart form functional specification, but i don't have any idea about how to prepare the functional specification?
can anybody send me the smart form functional specification template ?
which helps me to prepare the specification

Hi Devi,
Here is the FS for Form,
Functional Specification Document for Forms
Authors
Approved By
TABLE OF CONTENTS
1     OVERVIEW SECTION:     3
1.1     DOCUMENT OVERVIEW:     3
1.2     REVISION HISTORY:     3
1.3     OPEN ISSUES:     3
1.4     EXTERNAL REFERENCES:     3
1.5     REQUEST OVERVIEW:     3
1.6     GENERAL PROCESSING REQUIREMENTS:     4
2     BUSINESS/FUNCTIONAL REQUIREMENTS     5
2.1     REQUIREMENT DESCRIPTIONS:     5
2.2     BUSINESS DRIVER     5
2.3     TO-BE BUSINESS PROCESS:     5
2.4     TO-BE BUSINESS PROCESS FLOW DIAGRAM:     5
2.5     ASSUMPTIONS:     5
2.6     DEPENDENCIES:     5
2.7     RISKS:     5
2.8     SECURITY:     6
2.9     OTHER REQUIREMENTS:     6
3     FORM SECTION     7
3.1     REPORT SELECTION SCREEN:     7
3.2     STANDARD FORM NAME:     7
3.3     FORM LAYOUT:     7
3.4     DATA SOURCE:     7
3.5     SPECIAL REQUIREMENTS PROCESSING:     7
3.6     HOW TO EXECUTE THE FORM:     8
4     UNIT TEST PLAN SECTION     9
4.1     FUNCTIONAL UNIT TEST PLAN:     9
5     USER GUIDE REQUIREMENTS     10
5.1     USER GUIDE REQUIREMENTS:     10
6     APPENDIX     11
6.1     APPENDIX:     11
1     Overview Section:
1.1     Document Overview:
(Provide the high level identification information about the object to be developed. Id, title, Release etc)
Project      Project Atlas
Development Object ID:     SC-F-125
Development Object Title:     Purchase Order Form
Release:
Process Team:     Supply Chain
Process Area:     Procure-to-Pay
1.2     Revision History:
{This section should be filled with other details about the owner of functional specs, current status of document as explained in the status key etc}
Date Modified     Version     Modified By     Description of Change(s)
1.3     Open Issues:
(Any open issues should be reported in this section)
Issue #     Issue Date     Issue Title / Description     Priority     Resolved Date     Any Other Comments
1.4     External References:
(Identify any documents referenced in any part of this document. (Attach documents where possible.)
Document Title     Filename     Author     Identifier (Version/Date)
Process Flow diagram      N/A
Screen Shots if any     N/A
Sample data file     PO Form Layout (Single Page)     Erik Kraus     1/ (10/11/2006)
Sample data file     PO Form Layout (Multiple Pages)     Erik Kraus     1/ (10/11/2006)
1.5     Request Overview:
Complexity     0   High
1   Medium
0   Low
System(s) Impacted     1   R/3
0   CRM
0   BW
0
     0   Other
Existing SAP transaction(s) involved?     ME22N, ME23N
New SAP transaction(s) involved?     ME22N; then click Messages to print or Print Preview to view.
Menu path for transaction(s)     Logistics  Materials Management  Purchasing  Change
1.6     General Processing Requirements:
(Check the appropriate boxes for e.g. if the development object is an batch report that runs monthly, then check the Online and Monthly boxes in the Processing mode and frequency section and also provide the expected data volume if known)
Processing Mode:     1   Online
0   Batch
Frequency     0   Annually
0   Quarterly
0   Monthly
1   Daily
     1   Real Time
1   Ad-Hoc
1   Others
Expected Data Volume
2     Business/Functional Requirements
Section 2 describes what is needed. This information is used to build the design (how to do it) in Sections 3 and on
2.1     Requirement Descriptions:
Describe the purpose of the object. Brief overview
The purchase order form is used to display the purchase order in SAP. This form can also be sent to the supplier via e-mail or fax in SAP. The PO can also be displayed in the Print Preview screen and printed out as well.
2.2     Business Driver
The PO Form is standard in SAP. Modifications to the form will be necessary to meet the needs of the purchasing organizations at Sage. The PO form is necessary so that all the details of the purchase order can be faxed/ emailed to the supplier and also can be printed out into a hard copy form for internal purposes. The PO form also needs to be able to be viewed via the print preview icon in SAP.
2.3     To-Be business process:
Describe the To-Be business process
Customized Sage Purchase Order Form.
2.4     To-Be business process flow diagram:
Describe the To-Be business process flow diagram
N/A
2.5     Assumptions:
List all the assumptions that were made when developing this object
1)     Standard SAP PO Form will need to be modified from its standard layout.
2)     Font for Purchase Order form will be Times New Roman
3)     PO Form will be created in English
2.6     Dependencies:
List all the dependencies that were made when developing this object
N/A
2.7     Risks:
(What are the risks that make this development unique? What risks need to be proactively dealt with in order to be successful? What data sources are needed but not readily available? Are there any risks or concerns that make this development out of the ordinary?)
N/A
2.8     Security:
(Any security requirement for this object)
2.9     Other Requirements:
(If there are any other requirement which is not covered under section 2)
N/A
3     Form Section
Type:      0 SAP Script     1 Smart forms
3.1     Report Selection Screen:
Describe the selection screen of the program. Specify fields for selection and what checks are needed after the user has entered their criteria.
Field Name     Select Options / Parameters / Radio Buttons / Check Boxes     Default Values
From To     Validation
     Required /Optional     F4 Values
N/A     N/A     N/A     N/A     N/A     N/A
3.2     Standard form name:
Give the name of the SAP Script or Smart form name if copied from SAP
MEDRUCK Form in SAP
3.3     Form Layout:
Describe the form layout for each page.
The PO form will contain information at the Header Level, Item Level, and Authorizations levels.
Header Level:
The header level will contain all the supplier, bill-to party/address, and ship-to party/address information. The header level will also contain the payment and shipping terms, logo, page number, purchase order title, purchase order number, supplier number in SAP, and the PO date.
Item Level:
The item level will contain the item number, material and description, order unit, quantities, date required, unit cost, and the total amount of the line-item. The item-level will also contain the line-item text of purchase order.
Authorization:
The authorization section of the form will contain the name, telephone number, and email address of the purchasing agent.
Other:
-The Total Amount and Currency will be displayed to the right of the Authorization information.
-The layout will include sections and fields with borders. For example the Ship-To, Bill-To, and Supplier will be enclosed in rounded edge boxes. The Layout can be viewed in the Attachments section:
portion of section 3.4. which will show an example of a PO with only one page and a PO with multiple pages.
3.4     Data Source:
Identify the data that has to be appeared in the forms. Table Name-Field Name
All the fields will be available on the SAP standard form MEDRUCK. Any additional fields that are not on the standard form will need to be added. The mapping for additional fields not in the standard form will be shown below in each section (Header Level, Item-Level, and Authoriztions) if required.
Please see below for the required fields in the form:
This Section will contain details on the Header, Line-Item, and Authorization sections of the form. A section for attachements will also be inlcuded at the end.
I. Header Information:
The following fields will be displayed for the header information.
-     Title: Purchase Order
-     Logo: The Sage Software logo will appear in the top left corner of the form.
-     PO Creation Date (MM/DD/YYYY)
-     Supplier Number
-     PO Number
-     Page Number
-     Bill to Name and Address
-     Supplier Name and Address
-     Ship to Name and Adress
-     Payment Terms: (not on standard form, see field mapping section below)
-     Shipping Terms: (not on standard form, see field mapping section below). The shipping terms are the same as the incoterms in SAP. There are two fields for the incoterms and both will be used for the shipping terms.
-     Header Text
Additional Notes for Header Fields:
PO creation date should be in format MM/DD/YYYY
Page Number should be in format Page 1 of 1, Page 2 of 3, etc format
The Bill To name and address will come from the company code that is assigned to the plant in the purchase order.
The Ship To name and address will come from the storage location in the first line-item on the purchase order if the SC Vendor box is not checked on the delivery address tab of the purchase order. If the SC Vendor box is checked on the delivery address tab, then the Ship To address will come from the delivery address tab on the purhcase order from the central address management system.
The Supplier name and address will come from the vendor master in the purchase order.
The central address management system will need to be queried when looking up the Bill To, Deliver, and Supplier addresses.
Header Text: The text to be inserted here will be pulled from the Header Text in the purchase order.
Example: Text is pulled from the Header text with the green checkmark.
If the PO Form requires additional pages, then the header information should be duplicated on the subsequent pages.
Additional Fields :
Field Mapping for additional header fields that are not on the Standard SAP PO (MEDRUCK) Form . These fields can also be viewed on the PO Forms in the Attachments section.
PO Form Additional Fields
Field Name     SAP Table/ Field Name
Payment Terms     MEPO1226-ZTERM
Shipping Terms (incoterms1)     MEPO1226-INCO1
Shipping Terms (incoterms 2)     MEPO1226-INCO2
II. Item Level Information
The following fields will be on the PO form for the item-level:
-     Item Number
-     Material
-     Material Description
-     Unit (Unit of Measure)
-     Quantity
-     Date Reqd (MM/DD/YYYY)
-     Unit Cost
-     Amount
Each field will have an allotted amount of characters, so that all the text can fit on the line-item. Using .5 inch margins with times new roman 10pt font; there are 105 possible characters in microsoft word for the line-item details to fit on the line. The fields are broken down as follows with their allotted characters to accommodate the 105 allowed spaces:
Characters:
Item Number: 1-3
Material: 6-18
Descriptoin: 6-36
Unit: 39-49
Quantity: 44-56
Date Required: 60-69
Unit Cost: 77-86 (Commas and Delimals will be included in the Price. Two total decimal Spaces)
Amount: 92-103 (Commas and Delimals will be included in the Price. Two total decimal Spaces)
The Numbering Ranges above can be viewed below line-item 040 in the PO Form Outline (Sinlge Page) document in the Attachments section.
Note: These number ranges are shown as an example of what the form should like. They do not have to match up identicle to the specifications listed above.
Additional Notes for Line-Item Fields:
- Material Description will be displayed directly below the Material on the next line.
- Item Text: The Item text will be displayed if there are any item texts from the Purchase order. The text will be displayed two lines below the Material description. So there will be one line without any text. Also, the next line-item on the PO form will be displayed two lines below the item-level text; so there will be only one line with no text between the line-item with text and the subsequent line-item. Line items 020 and 030 depict this in the PO Form Outline_v1 document in the attachments section. The Line Item text will come from the Material PO text (identified below with a green checkmark) from the line-item on the purchase order as shown below.
- The Date Required Format will be MM/DD/YYYY.
- For every item in the purchase order, the program should loop through each item and check to see if the returns item box is checked (MEPO1211-RETPO). If this box is flagged on the purchase order, then the purchase order form needs to be updated with a return indicator. This indicator can be viewed on line-item 030 of the attached word document PO Form Outline (Single Page) in the Attachments section.
- The line-item fields should have the following alignment:
Material: Left
Material Description: Left
Unit: Left
Qty.: Right
Date Required: Left
Unit Cost: Right
Amount: Right
- If the line-items do not fit on one page, then they should continue on to subsequent pages. The Header information should be copied to all the subsequent pages and the authorization section will be displayed on the last page as well as the total amount and currency. This example can be viewed in document PO Form Outline (Multiple Pages) in the Attachments section.
Dislclaimer:
A disclaimer will also be included in this section and after all the line-items. The disclaimer text is still pending. An example of a disclaimer is shown in the PO Form Outline (Single Page) after line-item 040. This document can be found in the Attachments section.
If a PO requires multple pages, the the disclaimer will be displayed on the last page after the last line-item.
III. Authorization Information
This section will contain the purchasing agent: The purchasing agent will be the person who created the purchase order. This section will also contain their telephone number and email address.
The first and last name of the person who created the purchase order should be displayed here. This can be looked up in the users profile. The user profile will also contain their email and telephone number.
The field names for can be viewed below or in the PO Form Outline (Single Page) document in the Attachments section.
PO Form Additional Fields
Field Name     SAP Table/ Field Name
First Name     ADDR3_DATA-NAME_FIRST
Last Name     ADDR3_DATA-NAME_LAST
Telephone Number     SZA5_D0700-TEL_NUMBER
Email     SZA5_D0700-SMTP_ADDR`
Attachments:
3.5     Special Requirements Processing:
Describe the processing required to support any special requirements (e.g. signatures, logos, OCR, bar coding etc.).
3.6     How to execute the form:
Describe how to trigger the form e.g. Standard SAP transaction code or custom transaction code etc. If standard SAP transaction code describe the menu path
The form needs to be able to be viewed and printed.
To View:
Transaction ME22N or ME23N; Then Click the Print Preview   icon to view the Form.
To Print:
1) Transaction ME22N.
2) Click Messages
3) Select Output NEU and medium 1 Print output
4) Click the Further data button as shown in the screen shot above
5) Select 4 Send immediately (when saving the application)
6) Click Back   then Click Save
7) Select LOCAL for logical Destination
8) Click Save again
4     Unit Test Plan Section
4.1     Functional Unit Test Plan:
Document the criteria to be used for validating programming accuracy and positive/ negative results
Step     Scenario     Expected Results
Number     Description of what is being tested in this step     Description of what is expected to happen in this step
1     Go to Transaction ME22N and Display PO Form by clicking the Print Preview Icon     Form should mirror the forms in the Attachments section.
2     Go to Transaction ME22N and Print PO Form     PO Form should print as showed in the Print Preview Screen and the forms the Attachments section.
3     Create PO that will force PO form to cross multiple pages and then click Print Preview     PO Form should have Header information on all pages and line-item shoulds continue on to the subsequent pages. Authorization, Total Amount, Currency, and Disclaimer will be on the last page. The page numbers should also be correct and in the right format. This should mirror the PO Form Outline (Multiple Pages) document in the Attachments section.
4     Go to Transaction ME22N and print PO as in step 3     PO Form shoul print as showed in the Print Preview Screen and the PO Form Outline (Multiple Pages) document in the Attachments section.
5     User Guide Requirements
A User Guide must be provided to assist the person responsible for running the program(s). The User Guide must be in cookbook-style (required elements with step by step instructions) and annotated screen prints. The User Guide will be required in the running of the object in the Production environment as well as the QA and Test environments.
5.1     User guide Requirements:
N/A
6     Appendix
6.1     Appendix:
N/A
Hope it will help ..
Regards,
Arjun.
<b>Reward the points if it hepls</b>

Please update the functional specifications for Vendor Balance Report

Dear All,
Please update the functional specifications for Vendor Balance Report with
proper descriptions.
Please include
1. How your selection screen should look like..
2. Output format ( in an excel sheet)
3. Logic for every field in the output format (viz. .. how do link the
vendors from the selection screen to the BKPf and BSEG tables, how do you
find open and closed items in BSEG , etc.)
Please avoid statements like 'The total value of all the break-up should
tally with the balance as shown in FBL1N for a given vendor for the given
day.'
You need to give the logic for the FBL1N, in that case.
Regards
Rama Mohan

Hello again,
Regarding having them update the specs, one can dream. Dreams are free. LOL. Hopefully the memory makers will update their specs as more makers start supporting a large memory configuration.
The 4GB sticks I am using are http://shop.kingston.com/partsinfo.asp?ktcpartno=KTL-TP667/4G
I did not do an extended test of the sticks in my MBP. Their home is in the ThinkPad I have because it is running Windows Server 2008 with Hyper-V.
As you can see from the link above, these little suckers are pricey. But consider the price of 2GB SoDIMMs were $950 when they entered the market a couple of years ago. The price will drop.
I asked the Kingston rep that sent these to me if online sites like newegg.com would have them soon. She indicated no, but the corporate buying sites like CDW and Zone would. So check around. They just started shipped a couple of weeks ago so be patient.
If you have any other questions, please stop by http://blogs.technet.com/keithcombs/archive/2008/07/05/testing-my-apple-macbook- pro-with-8gb-of-ram.aspx and ask there. I'll see them much more quickly.
Cheers,
Keith Combs
Microsoft

Format of Functional Specification

What is the format of Functional Specification.

Hi refer belwo
Function Specs Format:
Document Control
Change History
Issue No
Date
Name
Change
Initial Draft
Authorizations
Role
Name
Signed
Date
Business Process Lead (customer)
Functional Analyst (specification author)
Technical Lead
Developer (if known)
Select program type below and then use menu option tools > unprotect to
open other fields for input
Type
Table of Contents
Document Control 1
Overview. 3
1.1 Short Description. 3
1.2 Business Process. 3
1.3 Terminology. 3
1.4 New Custom Objects Required. 3
1.5 Impacted SAP Transactions/Tables. 4
Process Decomposition. 5
2.1 Process Flow. 5
2.2 New Tables/Structures Required. 5
2.3 Sub-Process Description. 5
2.4 Error Handling. 5
2.5 Security Considerations. 5
2.6 Database Considerations. 5
2.7 Conversion Implications. 5
2.8 Batch Processing. 6
2.9 Functional Test Requirements. 6
Overview
1.1 Short Description
1.2 Business Process
1.3 Terminology
1.4 New Custom Objects Required
Include all new tables, key new fields/domains, new lock objects, new
match-codes, new transaction codes, new authorization objects, new
function groups, reports and module pools (transaction programs). Don't
specify all includes, function modules, routines etc. here.
Type (table, transaction etc.)
Description
Naming convention
1.5 Impacted SAP Transactions/Tables
List SAP objects updated/impacted by this specification (do not include
read only impacts)
Object(s)
Type (table, transaction etc.)
Description of Impact
Process Decomposition
2.1 Process Flow
2.2 New Tables/Structures Required
Specify new tables and structures required. If appropriate, you may
defer detailed field list/specification to the technical specification
(e.g. for secondary tables and structures).
Table id
Description
Type
Master, transaction, customizing, staging
Expected size
Maint. dialog
None, SM30, custom
Fields
Key
Domain/data element names
Domain format (if new)
Description
2.3 Sub-Process Description
2.4 Error Handling
Specify what to do if a condition passes AND fails (e.g. - what happens
if a customer record is found, or is not found). Specify messages and
type.
Specify any special error logging or table storage, including use of
standard application log where appropriate.
Field
Validation
Message type/no.
Message text
2.5 Security Considerations
2.6 Database Considerations
2.7 Conversion Implications
2.8 Batch Processing
2.9 Functional Test Requirements
Consider all the conditions that need testing for this enhancement and
document below. For each logic branch in theory both (or more)
conditions of the branch should be tested. For each scenario that could
impact program execution, all situations must be tested.
No.
Test condition
Expected result
Data set-up reqt.
Dependencies

HT4623 Hi, Im using an iPhone 4 8gb and recently updated my software using my computer to iOS 6.1.3 and some of the tabs are now grayed out and cant function (specific reference to "Show My Caller ID - On/Off tab"). is there a way to fix this or can i do

Hi, Im using an iPhone 4 8gb and recently updated my software using my computer to iOS 6.1.3 and some of the tabs are now grayed out and cant function (specific reference to "Show My Caller ID - On/Off tab"). is there a way to fix this or can i downgrade back to my default software?

Hi imobl,
Thanks for your response, I forgot to add that the five 3uk sims we have in use, I have tried all of them none of them are recongnised non of them have pin codes, I even purchased four more sims Tmobile (original carrier) Vodaphone, 3 and giffgaff.

Duplicate invoice, partial payment, residual payment

Hi every body
I am facing some problems in AP
1. I post a invoice in AP
I see that there are two document number 190000006
Please tell me why?
2. I pay a invoice with amount of 200000 in two times
firstly, I post a partial payment with amount 100000 (document number 1500000032)
secondly, I post a residual payment with remaining amount 100000 (document number 1500000033)
The invoice is paid completely and clear automatically but the are two documents (1500000032, 1500000033) is not cleared
Please tell me the payment process? how to clear payment document?
Thank in advance
Minh

Hi
Pls check SAP standard program RPBNUM00 for document numbers assigned more than once,
if your are using payment posting is using FB05 / F-53 transaction and in which Transfer Posting with clearing radio button is selected.
Let me know for any clarifications required
Regards,
suresh

In T code F-28, residual payment tab is hideout

Hi all,
In F-28 for making customer residual payment, tab option is not appearing, I checked in Accounting editing options(Fb00) there "process open items with commands" and " Enter payment amt for residual amounts" were already selected.
Eventhough the residual payment tab is hideout. Is there any thing we need to select for the tab.
Thanks & Regards,
Dharani

Hi Chintan,
Thanks for the reply. But there are no such validations.
Regards,
Dharani

Invoice reference for residual payment

HI experts
I observed if I receive the payment from customer Rs 10000 for the invoice Rs15000 through residual payment then system creates new line item for Rs 5000 and this will be shown as open item and all others will be clered items.
Here my issue is for new line item system is not storing the original invoice details in invoice reference field. How to maintain source invoice details to residual new line item.
Pls advice me
Thanks in advance
Sneha

Hi,
Anil is correct. All the details you entered in your incoming payment document when you posting your residual payment, will be displayed in the new line item created after that. My practice last time is that I will maintain the original invoice number at Reference field as suggested by Anil and entered my PO or SO number at Document header text.
If you don't wish to lose all the original details, you can use partial payment tab instead of residual. Partial payment will post the incoming payment without clearing any item. Then you can clear it off all together when you are posting for the last incoming payment for that particular invoice.
Hope this help.

Residual Payment vs. Partial Payment: Design considerations

We need to decide between implementing residual payment vs. partial payment. We will be implementing payment processing.
I would like to understand why one would choose one method over another?
What is the benefit of clearing original invoice and creating a new line item for the balance (as in case of residual payments)? There is a setting that allows user to capture the original invoice date at the time of payment processing while using residual payment, which I believe makes the residual payments same as partial payments, so again, why would one choose one method over another?
I would like to understand the benefits & limitations of each method.
How does the decision to implement a method get impacted if reason codes are to be implemented, which method would offer a better solution considering reason codes requirement?
Appreciate your inputs.

Hi,
In manual processing of incoming payments, it is of course the user who can make the decision to either make residual item, or a partial payment.
In automatic processing of incoming payments:
For electronic bank statements, payments that the system cannot match with open items will end up in post-processing; there the user can again choose either residual item or partial payment.
For electronic payment advices, I know that there is configuration to match customer information for payment deductions in the payment advice, with you own reason codes, and that based on the information the system can create the residual items automatically. Of course, this is only relevant if your customers actually send you electronic payment advices with such information included.
Regarding reason codes, you will always use reason codes with residual items; to indicate the reason for deduction for follow up in your A/R dept, and possibly to make use of the automatic write off (you can configure reason codes to automatically write off the payment deduction to some G/L account of your choosing; you would use that e.g. if the payment deduction is too small to bother).
For partial payment, you could use reason codes I guess, if you want to in that way mark the item for some reporting or follow up purpose.
Regards,
Rob

FUNCTIONAL SPECIFICATIONS OF AN HR REPORT

I WOULD BE REALLY GREATEFUL,IF SOMEBODY CAN SEND ME THE FUNCTIONAL SPECIFICATION OF ANY BASIC HR REPORT.
I HAVE JUST COMPLETED MY COURSE AND I'M PRACTICING. i LOOKED FOR IT ON THE NET BUT COULD NOT FIND ANY.

post ur HR related ?'s in
HR(ECM)

Functional Specifications for ABAP Developments

Dear All,
We are implementing negative time management. We require data to be transferred from the Time Recording Terminal to the SAP system. We are planning to adopt for ABAP program to transfer data from Time Recording System to SAP. Can anyone provide me with the functional specifications I should be providing to the ABAP consultants. Also please provide the Standard format we should follow to give Functional Specs to the ABAP consultants.
Regards,
T.Satish

Dear Christopher,
Our customer has existing Time Recording terminals(TRT). These TRT's do not have an interface with SAP. The data is downloaded in "text" format from the TRT. We are planning to develop a BDC for the data transfer. I am required to give the Functional Specs for this purpose. If possible please give me a copy of the functional specs prepared for data transfer from TRT to SAP.
Regards,
T.Satish

Functional specifications on F-32 residual payment

Similar Messages

Maybe you are looking for