Create incoming payments, based on Sales Person code

Hi all,
is there any SAPB1 functionality to create incoming payments, for many Sales Invoices of different customers , based on a Sales Person code ?
Thank you,
Aris Pantelatos

Hi Jitin and Gordon,
Thank you both for your replies.
Jitin, I need to create different incoming payments (one for every customer) based on a list of invoices with a specified Sales Person on them.
Do you know, if this is included on SAPB1 roadmap?
Aris
Edited by: Aris Pantelatos on Feb 8, 2012 4:04 PM

Similar Messages

How to do an incoming payment based on journal entry whit SDK ?

Hello
Somebody have the code for SDK of Business One, how to do an incoming payment based on journal entry?
Tks

Hello Julio,
Here some example code from the SDK helpfile.
Private Sub cmdTest_Click()
 On Error GoTo ErrorHandler
 Dim vCompany As SAPbobsCOM.Company
 'create company object
 Set vCompany = New SAPbobsCOM.Company
 'set paras for connection
 vCompany.CompanyDB = "SBODemo_US"
 vCompany.Password = "manager"
 vCompany.UserName = "manager"
 vCompany.Server = "(local)"
 'connect to database server
 If (0 <> vCompany.Connect()) Then
 MsgBox "Failed to connect"
 Exit Sub
 End If
 Dim nErr As Long
 Dim errMsg As String
 'Set the object's properties
 Dim vPay As SAPbobsCOM.Payments
 Set vPay = vCompany.GetBusinessObject(oIncomingPayments)
 vPay.Address = "622-7"
 vPay.ApplyVAT = 1
 vPay.CardCode = "D10006"
 vPay.CardName = "Card D10004"
 vPay.CashAccount = "288000"
 vPay.CashSum = 0
 'vPay.CheckAccount = "280001"
 vPay.ContactPersonCode = 1
 vPay.DocCurrency = "Eur"
 vPay.DocDate = Now
 vPay.DocRate = 0
 vPay.DocTypte = 0
 vPay.HandWritten = 0
 vPay.JournalRemarks = "Incoming - D10004"
 vPay.LocalCurrency = tYES
 vPay.Printed = 0
 vPay.Reference1 = 8
 vPay.Series = 0
 vPay.SplitTransaction = 0
 vPay.TaxDate = Now
 vPay.TransferAccount = "10100"
 vPay.TransferDate = Now
 vPay.TransferSum = 0
 vPay.Invoices.AppliedFC = 0
 vPay.Invoices.AppliedSys = 0
 vPay.Invoices.DocEntry = 8
 vPay.Invoices.DocLine = 0
 vPay.Invoices.DocRate = 0
 vPay.Invoices.InvoiceType = 13
 vPay.Invoices.LineNum = 0
 vPay.Invoices.SumApplied = 5031.2
 Call vPay.Invoices.Add
 Call vPay.Invoices.SetCurentLine(1)
 vPay.Invoices.AppliedFC = 0
 vPay.Invoices.AppliedSys = 1089.65
 vPay.Invoices.DocEntry = 11
 vPay.Invoices.DocLine = 1
 vPay.Invoices.DocRate = 0
 vPay.Invoices.InvoiceType = it_Invoice
 vPay.Invoices.LineNum = 1
 vPay.Invoices.SumApplied = 1000
 vPay.CreditCards.AdditionalPaymentSum = 0
 vPay.CreditCards.CardValidUntil = CDate("10/31/2004")
 vPay.CreditCards.CreditAcct = "295000"
 vPay.CreditCards.CreditCard = 3
 vPay.CreditCards.CreditCardNumber = "884848448"
 vPay.CreditCards.CreditCur = "EUR"
 vPay.CreditCards.CreditRate = 0
 vPay.CreditCards.CreditSum = 5031.2
 vPay.CreditCards.CreditType = 1
 vPay.CreditCards.FirstPaymentDue = CDate("11/29/2002")
 vPay.CreditCards.FirstPaymentSum = 5031.2
 vPay.CreditCards.LineNum = 0
 vPay.CreditCards.NumOfCreditPayments = 1
 vPay.CreditCards.NumOfPayments = 1
 vPay.CreditCards.OwnerIdNum = "3993939"
 vPay.CreditCards.OwnerPhone = "383838888"
 vPay.CreditCards.PaymentMethodCode = 1
 Call vPay.CreditCards.Add
 Call vPay.CreditCards.SetCurentLine(1)
 vPay.CreditCards.AdditionalPaymentSum = 0
 vPay.CreditCards.CardValidUntil = CDate("10/31/2004")
 vPay.CreditCards.CreditAcct = "295000"
 vPay.CreditCards.CreditCard = 3
 vPay.CreditCards.CreditCardNumber = "884848448"
 vPay.CreditCards.CreditCur = "EUR"
 vPay.CreditCards.CreditRate = 0
 vPay.CreditCards.CreditSum = 1000
 vPay.CreditCards.CreditType = 1
 vPay.CreditCards.FirstPaymentDue = CDate("11/29/2002")
 vPay.CreditCards.FirstPaymentSum = 1000
 vPay.CreditCards.LineNum = 1
 vPay.CreditCards.NumOfCreditPayments = 1
 vPay.CreditCards.NumOfPayments = 1
 vPay.CreditCards.OwnerIdNum = "3993939"
 vPay.CreditCards.OwnerPhone = "383838888"
 vPay.CreditCards.PaymentMethodCode = 1
 If (vPay.Add() <> 0) Then
 MsgBox ("Failed to add a payment")
 End If
 'Check Error
 Call vCompany.GetLastError(nErr, errMsg)
 If (0 <> nErr) Then
 MsgBox ("Found error:" + Str(nErr) + "," + errMsg)
 Else
 MsgBox ("Succeed in payment.add")
 End If
 'disconnect the company object, and release resource
 Call vCompany.Disconnect
 Set vCompany = Nothing
 Exit Sub
ErrorHandler:
 MsgBox ("Exception:" + Err.Description)
End Sub
HTH Regards Teun
Edited by: Teun Aben on Aug 4, 2010 9:00 PM

Create a payment based on a journal entry document

Hello!
In SBO 2007A PL44 I could add an incoming payment based on journal entry, but my code doesn't work in PL46.
It's a bug?
The Code:
 Dim oPay As SAPbobsCOM.Payments = oCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oIncomingPayments)
 oPay.DocType = SAPbobsCOM.BoRcptTypes.rCustomer
 oPay.DocDate = Today
 oPay.TaxDate = Today
 oPay.DueDate = Today
 oPay.VatDate = Today
 oPay.CardCode = "310000010"
 oPay.Invoices.DocEntry = 1882
 oPay.Invoices.InvoiceType = SAPbobsCOM.BoRcptInvTypes.it_JournalEntry
 oPay.Invoices.SumApplied = 12000
 oPay.CashAccount = "38117000"
 oPay.CashSum = 12000
 oPay.DocCurrency = "Ft"
 If oPay.Add <> 0 Then
 Dim errCode As Integer = 0
 Dim errmsg As String = ""
 oCompany.GetLastError(errCode, errmsg)
 End If
I got the following error:
errCode: -10
errMsg: Cannot pay partial down payment
Regards Csaba
Edited by: Csaba Fülöpcsei on Apr 8, 2009 4:49 PM

Dear Jane Jing!
Yes I have a issue in B1 app for this payment:
In Incoming payments windows select the customer doctype and select the customer (310000010), and the list of the invoices check the line (1882, journal entry) and type 10000 in the Total Payment column. And after 'Payment Mean' icon, I can add the payment.
The problem is still on all payments of jourlnal entries from DI API.
If I assign any value to oPay.Invoices.SumApplied field, I couldn't add the payment.
Regards Csaba

Create Incoming payment from an A/R Invoice

Hello,
I am on SBO2005A SP01 PL39 and do not find the option to create Incoming payment from an existing Invoice. When I open an existing A/R Invoice and click on CopyTo it shows only A/R Credit Memo. I remember seeing the Incoming Payment option in the earlier patch. Does this mean I cannot create an Incoming Payment based on an A/R Invoice?
Thanks and Regards,
Sheetal

Sheetal,
Just to clarify, the Incoming Payment has never been available as a Copy to option from Invoice.
The Incoming Payment resides inside the Banking module.
From Main Menu > Banking > Incoming Payment ...Incoming Payment
The only time the Payment Means window will automatically open when you Add the Invoice is when the Payment Terms of the Business Partner is setup to open Payment Means window.
Suda

Error on creating Incoming Payment that links to another Incoming Payment

Hi Experts,
I am trying to create an Incoming Payment to pay an Invoice, as well as to use another Incoming Payment with an open balance (with Payment On Account box checked) to offset part of this payment.
Conceptually...
Incoming Payment A (-$75)
 --- link to Invoice B ($85)
 --- link to Incoming Payment C (-$10)
This can be done manually, but by using DI API, I am facing this error:
"-10: Base document card and target document card do not match. (RCT2.DocLine)(line: 2)"
Here is the source code:
Dim oPayments As Payments = DirectCast(oCompany.GetBusinessObject(BoObjectTypes.oIncomingPayments), Payments)
' [HEADER]
oPayments.CardCode = "C0001"
oPayments.DocDate = Today
oPayments.DocType = BoRcptTypes.rCustomer
oPayments.CashSum = 0
oPayments.BankChargeAmount = 0
oPayments.TransferAccount = "12180208"
oPayments.TransferDate = Today
oPayments.TransferSum = 75
oPayments.LocalCurrency = BoYesNoEnum.tYES
' [LINE 1 - AR Invoice B.]
oPayments.Invoices.InvoiceType = BoRcptInvTypes.it_Invoice
oPayments.Invoices.DocEntry = 16949
oPayments.Invoices.SumApplied = 85
' [LINE 2 - Incoming Payment C with Open Balance.]
oPayments.Invoices.Add()
oPayments.Invoices.InvoiceType = BoRcptInvTypes.it_Receipt
oPayments.Invoices.DocEntry = 20338 ' Journal Entry Number of the Incoming Payment
oPayments.Invoices.SumApplied = -10
If oPayments.Add() <> 0 Then
 oCompany.GetLastError(errCode, errMessage)
 BarError(String.Format("{0}: {1}", errCode, errMessage))
Else
 BarSuccess("Success.")
End If
Initially I tried to set
oPayments.Invoices.DocEntry
with the Incoming Payment's DocEntry, but after trial and error, I realized I should be using the Incoming Payment's Journal Entry's Number instead. So this field should be correct. (If I were to use the Incoming Payment's DocEntry for this field, I get the "-2028: No matching records found (ODBC -2028)" error.)
I have ensured that the Incoming Payment C's CardCode is the same as the one I set in
oPayments.CardCode
, so I'm not sure why it gives an error saying the document cards do not match. I would appreciate any form of help on this! Thanks!

Hi,
I am not trying to Pay to Account (you are referring to the top left radio button of the Incoming Payment right?). I am trying to create an Incoming Payment that uses another over-paid Incoming Payment (i.e. Open Balance > 0) to offset its Amount Due.
Anyway I have found the solution to my problem. It seems that I need to also set the
oPayments.Invoices.DocLine
value to the over-paid Incoming Payment's Journal Entry's document line which contains the same business partner as my Incoming Payments. This DocLine value is usually 1 (0-based), as SAP usually creates the Journal Entry with the BP row in the second row.

Incoming payment by F-28: Reason code error while posting

Hello everyone,
I want to post Incoing Payment using F-28 net of TDS. I want the separate GL account to be picked up automatically for the difference when I enter the Reason Code 003.
I did the following customization for the same.
1. Financial Accounting> Accounts Receivable and Accounts Payable> Business Transactions>Incoimng Payments> Incoming Payments Global Settings>Overpayment/Underpayment> Define Reason Codes:- Here I selected the Indicator 'C' for reason code 003 which is for "Indicator: Charge off difference via separate account". The reason code 003 is for TDS Netted
2. Below the Define Reason Code node, I selected the node 'Define Accounts for Payment Differences' . Selected the key ' Rules' and selected the checkbox 'Reason Code'. Then clicked on 'Accounts' and enetered the desired GL account against the reason code '003'.
After doing the above customization I posted the Incoming payment using T code F-28. I entered the difference in the field 'Difference Posting'. Then entered reason code '003' which is for 'TDS netted' in the field 'Reason Code'. Now, I am getting the follwoing error.
Reason codes with automatic charge-off are not permitted here
Message no. F5605
Diagnosis
The reason code entered is designed to ensure that the payment difference amount is posted to an account specially set up for this purpose. Postings of this nature usually require additional specifications (e.g. tax code, business area). If the difference stems from a single open item, the necessary specifications can be taken from that item. In the case that led to this error message, however, the difference does not stem soley from one item, which means that this method cannot be used.
System Response
The reason code entered is not accepted.
Procedure
You can either select a different reason code, which would create a new open item for the customer or vendor OR write off the difference using the function Charge off diff.. This function either takes you into a pre-configured account assignment model or into the document overview. From here you can enter the required difference postings.
How can I proceed ahead?
Thanks and Regards,
Pradnya

Hi Saulo,
Thanks for ur reply.
I had alreay done the config in OBXL and OBBE. Only thing I wanted to know is while posting Incoming Payment by F-28, how to use this reason code.
Ur reply was a gr8 help for me.
Regards,
Pradnya

F-28 - Incoming payments with residual items - Vat code

Dear all,
I need to define a process in which the user can create a residual item for a downpayment on an incoming payment from a customer, and the system automatically creates a new document with the residual posting.
I have done the customizing for the "Residual Item Posting in Invoice Currency" and defined a Type of document for the residual item. The problem is that the standard procedure puts the vat code also in the payment document and in the residual item document on the customer position... and this is not correct.
Someone can help me?
Thank you
Regards
Marco.

Yes, this is due to settings on GL Account for reconciliation account. Please fo t o FS00 provide reconciliation account nr (if down payment) from Sp. GL an d not from Vendor / Customer master and change settings on second tab > there is mantioned that posting without tax are not allowed. (input tax / only output tax only).
Due to GL master data he post always with the VAT. Addtionally if You will have a discount system will correct the VAT line with discount during clearing all of that becasue of GL master data.
Regards
Tadeusz

Error creating incoming payment. (ODBC -2035)

The error that I get while creating an incoming payment is:
This entry already exists in the following tables (ODBC -2035)
Here is the code:
public static bool CreatePayment()
       DateTime now = DateTime.Now;
       Payments pmt = (Payments) m_company.GetBusinessObject(BoObjectTypes.oIncomingPayments);
            pmt.ApplyVAT = BoYesNoEnum.tYES;
            pmt.CardCode = invoice.CardCode;
            pmt.CardName = invoice.CardName;
            pmt.CashSum = 0;
            pmt.ContactPersonCode = invoice.ContactPersonCode;
            pmt.DocCurrency = invoice.DocCurrency;
            pmt.DocDate = now;
            pmt.TaxDate = now;
            pmt.DocRate = 0;
            pmt.LocalCurrency = BoYesNoEnum.tYES;
            pmt.DocType = BoRcptTypes.rCustomer;
            pmt.HandWritten = BoYesNoEnum.tNO;
            pmt.JournalRemarks = "journal remarks";
            pmt.Remarks = "remarks";
            pmt.Reference1 = baseEntry.ToString();
            pmt.TransferSum = 0;
            // invoice
            pmt.Invoices.AppliedFC = 0;
            pmt.Invoices.DocEntry = baseEntry;
            pmt.Invoices.DocLine = 0;
            pmt.Invoices.InvoiceType = BoRcptInvTypes.it_Invoice;
            pmt.Invoices.SumApplied = amount;
            // credit card
            pmt.CreditCards.AdditionalPaymentSum = 0;
            pmt.CreditCards.CardValidUntil = Util.CCDateToDateTime(cardExpirationDate);
            pmt.CreditCards.CreditCard = bp.CreditCardCode;
           pmt.CreditCards.CreditCardNumber = ccNumber;
            pmt.CreditCards.CreditSum = amount;
            pmt.CreditCards.CreditType = BoRcptCredTypes.cr_InternetTransaction;
            pmt.CreditCards.FirstPaymentDue = now;
            pmt.CreditCards.FirstPaymentSum = amount;
            pmt.CreditCards.NumOfCreditPayments = 1;
            pmt.CreditCards.NumOfPayments = 1;
            // there's a record in OCRP (credit card payment methods)
            pmt.CreditCards.PaymentMethodCode = 1;
            if (pmt.Add() != 0)
                int errCode;
                string errMsg;
                m_company.GetLastError(out errCode, out errMsg);
                // here errMsg is "This entry already exists in the following tables (ODBC -2035)"
                return false;
            return true;
I had 53 records in ORCT (incoming payments) but the next number in NNM1 and ONNM was 1. So I assumed that it was wrong and tried to set NNM1.NextNumber and ONNM.AutoKey to 54 for ObjectCode = 24 (Incoming payment).
The error remained the same. Then I removed all records from ORCT and its subordinate tables RCT1, RCT2, RCT3,.... and changed the next number back to 1.
The error is still: "This entry already exists in the following tables (ODBC -2035)".
Do you have any ideas what may cause the above error and how I can get more info which is the entry that already exists and in which table?
The code above works on another company (database).
Thanks.
Svilen

Thanks Alexey,
Please note that I have manually modified SBO tables once the problem appeared not before. I do not know how receipt numbers got out of sync.
I also find the message "This entry already exist in the following
tables" without actually specifying any table, strange, the least.
The SDK is not particularly good and the samples in the help file are outdated and therefore wrong.

No matching record found when creating Incoming Payment...

Hi,
I'm starting a transaction, creating a invoice and then creating a incoming payment.
The invoice is created successfuly in memory I can see the next DocEntry and DocNum and passing it to the incoming payment as usual but I'm getting the error : No matching records found
Any idea ?

I found why.
The Series used was not there. But it's not obvious to know that it's because you set a wrong Series code with an error like this.

Create bullling doc. based on sales office

Hi All,
I have one scenario like ,
we need to find out the T-Code which is creating the billing document based on sales office.
For example we dont want to create billing for sales office 4017.
This is running in background.
Thanks,
Amjad

Hi!
Have you tried VF06 transaction?
If it does not know it in standard, just copy the program RV60SBAT into a ZRV60SBAT, add your field to the selection screen, code it into the select and that's all.
Regards
Tamás
Message was edited by:
Tamás Nyisztor

Create Purchase Order based on Sales Order through DI

Hi All,
As per my requirment i need to create PO based on Sales Order by Using DI object.
By using the UI i am able to create a PO. i.e,. in the Sales Order Form , in logistic tab when the purchase check box is checked and when the SO is added there is a work around form poped up where we give the vendor information and create PO.
Code:
      objPurchaseOrder = objSBOAPI.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oPurchaseOrders)
                                    objPurchaseOrder.CardCode = "V1010"
                                        objPurchaseOrder.CardName = "Far East Imports"
                                        objPurchaseOrder.DocDate = "02/24/05"
                                        objPurchaseOrder.DocDueDate = "02/24/05"
                                    objPurchaseOrder.Lines.BaseType = "17"
                                    objPurchaseOrder.Lines.BaseLine = "0"
                                     objPurchaseOrder.Lines.BaseEntry = "35"
                                         objPurchaseOrder.Add()
Error Description : Base Doc Type donot match with target Doc type
PLease help me
Thanks and Regards
Sandeep

hi,
try removing the double quotes for basetype, baseline, baseentry.
if it doesn't solve the problem
make sure that you are assigning the docentry only but not the docnum of the sales order to the purchase order lines' baseentry.
rgds,laks.

Can one incoming payment matches with few BP code's invoices?

Hi,
My scenario is the HQ paying for the branch offices in one cheque but the branch offices having their own business partner code in the database. Can user make one incoming payment and select the invoices to match from few different business partner?
I realised this can be done if we use the Consolidate BP function in BP master but this will make the statement of accounts to be consolidated as well. Anyway that if this function is activated but statement of accounts does not combined? Kindly advise, thanks.
Regards,
MH

Hi,
What i mean is that can all those BP's statement is not consolidated into one statement instead of separate?
Current setting is once consolidate BP function is activated, all related BP's statement will be consolidated. Any workaround to separate the statement?
Thanks.

How to create batch job based on sales organization?

I am Sending data using RFC function module, within a report program.
Now according to functional requirement I have to create two batch job scheduling scenarios:
1. Provide a batch job to be run towards month end (2X, 1X) to sent a delta record message using Report. This is scheduled on demand or requested on demand. Recommend 1 message per sales org.
Q: What does it mean by scheduled on demand or requested on demand?? Second thing is that like we have 10 sales org. and in variants for job scheduling we can assign only 1 at a time......how can i schedule per sales organization? do i need to create different job for each sales organization??
(2X, 1X) what is the meaning of this notation??
2. Create a new nightly batch job, run after daily billing batch, to send a delta records message of Report. Recommend 1 message per sales org.
Anyone please provide me some details on this issue.......
Regards
Anshul

I am Sending data using RFC function module, within a report program.
Now according to functional requirement I have to create two batch job scheduling scenarios:
1. Provide a batch job to be run towards month end (2X, 1X) to sent a delta record message using Report. This is scheduled on demand or requested on demand. Recommend 1 message per sales org.
Q: What does it mean by scheduled on demand or requested on demand?? Second thing is that like we have 10 sales org. and in variants for job scheduling we can assign only 1 at a time......how can i schedule per sales organization? do i need to create different job for each sales organization??
(2X, 1X) what is the meaning of this notation??
2. Create a new nightly batch job, run after daily billing batch, to send a delta records message of Report. Recommend 1 message per sales org.
Anyone please provide me some details on this issue.......
Regards
Anshul

Post incoming payments based on Invoice number.

Hello,
I would appreciate your help on the following question. POINTS AVAILABLE. Is there a way for us to post an incoming partial payment from a customer based only on the invoice number?
For example, a customer has several open invoices and want to make a partial payment on 1 of the invoices. I know we can do it using F-28 (Partial Payments tab), however, is there any other way to post a payment to a particular invoice without entering a customer number? Using F-28 brings up all the invoices and pmts for the customer.
Thanks in advance!

This is the documentation about the program:
F.13
This program clears open items from customer, vendor and G/L accounts (in particular, GR/IR clearing accounts) automatically.
It selects all accounts specified in the value sets that have debit and credit postings.
The following items are not cleared:
Noted items
Statistical postings and special G/L transactions of the type bill of exchange
Items with withholding tax postings
Down payments can only be cleared if down payment clearing for the same amount has been posted
The remaining open items are grouped according to fixed system criteria:
Company code
Account type
Account number
Reconciliation account number
Currency key
BSID-WAERS for customers
BSIK-WAERS for vendors
BSIS-PSWSL for G/L accounts
Special G/L indicator
The program also groups items according to a maximum of five user criteria. Note that the trading partner number and the business area are no longer fixed system criteria (in comparison to the former clearing programs SAPF123 and SAPF123W). Therefore, if you want to group by business area or trading partner number, you have to enter these as user criteria.
Clearing takes place when, for the group of line items selected according to the above criteria, the balance in document currency (for customers and vendors) or in update currency (for G/L accounts) is zero. The date for clearing is the clearing date according to your selection specifications. In an update run, if the clearing transaction is successful, the clearing document number is specified.
During the program run, all accounts in which clearing can be performed are blocked. They are then unblocked again after the clearing transaction. Accounts that are blocked by other transactions or that are intended for the automatic payment run are not considered in automatic clearing
OB74
Prepare Automatic Clearing
In this activity you enter the criteria for grouping an account's open items for automatic clearing. The clearing program clears the open items that are grouped together if their total balance equals zero in local and foreign currency.
You must enter the following standard criteria:
account type
account number or a number interval
You can also enter a further five criteria.
You select these five additional criteria from the fields in table
BSEG or BKPF. If possible, you should choose fields that are also
contained in table BSIS (G/L accounts), BSID (customers), or BSIK
(vendors). You can determine the field names by displaying the tables
in the Data Dictionary, which you reach by choosing
Tools -> ABAP Workbench and then Dictionary.

How to Create Task Automatically based on Sales Stage?

If an Opportunity's Sales Stage is changed from 'X' to "Y',then I want to create the Task for an Agent automatically by the System.How can we achive it?Could you please elaborate steps that we need to this (If customisation,how ca we do it?)
Thanks in Advance
Raju.

First U have to crate Extended View Object to your actual View obj.
Now take Page with Panel Splitter ,on First facet drag View obj as table and on second Facet Drag Extended View Obj as table.On page loading U have delete all rows from Extended View object.And then u have write bean code on button click to get current select rows from above view objct,and for Filter rows from Second View obj according to selection of rows from first view obj...

Create incoming payments, based on Sales Person code

Similar Messages

Maybe you are looking for