Payment Gauranteed Procedure

Dear Gurus,
In my customer master "Payment Gauranteed Procedure" field is not appearing, kindly advise.

Ok, go the Tcode.
Regards,

Similar Messages

Payment Gauranteed Procedure Field

Dear Gurus,
In my customer master payment gaurantee procedure field is not appearing, but when i am in display mode its appeared.
what is the possible cause.
2ndly status in the financial document is freeze I am not in a position to change them only "the document is created" status is updated".
Pls advise.

Issue resolved.
We can assign this through SPRO setting.
That also fulfill the same purpose too.
Regards,

Payment Guarantee Procedure not appearing automatically in the sales order

Hi All,
I have configured the risk management following all the steps as below but somehow the payment guarantee procedure does not auto appear in my sales order.
Step 1: Financial Document Type
Step 2: Field Controls in Fin Doc Type
Step 3: Financial Document Control
Step 4: Maintain Forms of Payment Guarantee
Step 5: Define & Assign Payment Guarantee Procedure
Step 6: Customer Payment Guarantee Procedure
Step 7: Assign Doc Procedures to Order Types
Step 8: Payment Guar.Procedure Determination
Kindly advise if I have missed out any steps

Hi,
please check
1 . Define Payment Guarantee Schema Determination
2 . Activation of credit for item category
With regards,
Mrinal

Payment Guarantee Procedure

hi
When i created a SO, Payment Guarantee Procedure's value in Billing Document tab was '000001'(Letters of credit) automatically, and there is one error log when clicking on the 'Finance Doc. List' button.
Now, anyone can tell me why the error log will be presented?hope some one can help me, thanks a lot

Dear Quanyin
Can you please let us know what the error message is ??
For information, in VX11N, an L/C is created and saved and its reference number is assigned in your sale order. If you try to deviate from the conditions what you maintained in VX11N, then system will not allow you to generate billing.
You can recheck in VK12N.
thanks
G. Lakshmipathi

Payment guarantee procedure key in customer master

Hi ,
System determines payment guarantee procedure by
1. key for doc guarantee proc from sales doc type
2. customer payment guarantee procedure key in customer master
However , I am not able to find the field in XD02 for maintaining cust payment guarantee procedure.
Can some one help me in locating that field . Can this customer master screen be controlled through field screen.
Regards,
Mrinal

Mrinal,
in Customer master , we can see the field in Sales area data billing tab.
But if u are nt able to see in that then i guess that fields are suppresed.
For seeing that do this
go to transaction OVT0
select your account group then On Field Status group, double click on the word Sales data then on the word Billing.
In this go to Hedging and credit contr. area which may be suppressed, it means that the field above is not visible in the customer master data. Make this fields visible.
Thanks,
Raja

How to configure payment cards procedure

hi,
can someone through some light how to go about it .
Regards
Anil

Hi Friend,
Set Up for Credit Card Payment Processing
Given below is the set up for credit card payment processing:
01. Set Up Credit Control Areas:
02. Define Credit Control Area
Transaction: OB45
Tables: T014
Action: Define a credit control area and its associated currency. The Update Group should be 00012. This entry is required so the sales order will calculate the value to authorize
03. Assign Company Code to Credit Control Area
Transaction: OB38
Tables: T001
Action: Assign a default credit control area for each company code
04. Define Permitted Credit Control Area for a Company
Code
Transaction:
Tables: T001CM
Action: For each company code enter every credit control area that can be used
05. Identify Credit Price
Transaction: V/08
Tables: T683S
Action: Towards the end of the pricing procedure, after all pricing and tax determination, create a subtotal line to store the value of the price plus any sales tax. Make the following entries:
Sub to: A
Reqt: 2
AltCTy: 4
06. Automatic Credit Checking
Transaction: OVA8
Tables: T691F
Action: Select each combination of credit control areas, risk categories and document types for which credit checking should be bypassed. You need to mark the field no Credit Check with the valid number for sales documents.
07. Set Up Payment Guarantees
08. Define Forms of Payment Guarantee
Transaction: OVFD
Tables: T691K
Action: R/3 is delivered with form 02 defined for payment cards. Other than the descriptor, the only other entry should be 3 in the column labeled PymtGuaCat
09. Define Payment Guarantee Procedure
Transaction:
Tables: T691M/T691O
Action: Define a procedure and a description.
Forms of Payment Guarantee and make the following entries Sequential Number 1
Payment Guarantee Form 02
Routine Number 0 Routine Number can be used to validate payment card presence.
10. Define Customer Payment Guarantee Flag
Transaction:
Tables: T691P
Action: Define a flag to be stored in table.
Create Customer Payment Guarantee = Payment Card Payment Cards (All Customers can use Payment Cards).
11. Define Sales Document Payment Guarantee Flag
Transaction:
Tables: T691R
Action: Define the flag that will be associated with sales document types that are relevant for payment cards
12. Assign Sales Document Payment Guarantee Flag
Transaction:
Tables: TVAK
Action: Assign the document flag type the sales documents types that are relevant for payment cards.
13. Determine Payment Guarantee Procedure
Transaction: OVFJ
Tables: T691U
Action: Combine the Customer flag and the sales document flag to derive the payment guarantee procedure
14. Payment Card Configuration
15. Define Card Types
Transaction:
Tables: TVCIN
Action: Create the different card types plus the routine that validates the card for length and prefix (etc)
Visa , Mastercard, American Express, and Discover
Create the following entries for each payment card
AMEX American Express ZCCARD_CHECK_AMEX Month
DC Discover Card ZCCARD_CHECK_DC Month*****
MC Mastercard ZCCARD_CHECK_MC Month
VISA Visa ZCCARD_CHECK_VISA Month
The Routines can be created based on the original routines delivered by SAP.
links:
http://help.sap.com/saphelp_erp2005vp/helpdata/en/a6/b1853478616434e10000009b38f83b/frameset.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/SDBILIVPC/SDBILIVPC.pdf

Customer payment guarantee procedure

Hi,
How can I assign the amount of the "Customer payment guarantee procedure", because I set the type of the payment guarantee of the master data (XD02) but I cannot find the way to assign the amount.
Should I create a FI document? How can FI/SD document be related?
Thanks,
Cecilia

hi
in XD02 you cannot find the payment amount to enter but you can find an payment gurantee procedure how and where and when the customer will pay your money for the goods.
sorry for sending:
http://help.sap.com/saphelp_47x200/helpdata/en/93/744a0a546011d1a7020000e829fd11/frameset.htm
balajia

Payment Grantee Procedure

Hello
In Sales Order Header.... Billing Tab there is a Payment Grantee Procedure and Financial Document Number. What is the use of these fields in Foreign Trade Data. How are these fields determined in Sales order and what is the impact of these fields on the subsequent Document.
Thanks and Regards
Prashant Ranalkar

Hi Prasant,
Below is help link for Payment Guarantee process....
[Payment Guarantee procedure|http://help.sap.com/saphelp_45b/helpdata/en/2a/30b749b1d511d194f300a0c9306794/frameset.htm]
Financial Document number is Internal number of a financial document. The number is assigned by the System itself.....
The Use of Payment Guarantee process comes under Risk management.....
For example if u are sending some product to Foreign country......So for taking payment there is variouos methiods and Risks associated......i.e Whether the customer give the money or nt? etc.... For this Payment Guarantee form is used..... Now a days we also use Letter of Credit.....
Thanks,
Raja

I have to supress one field named PAYMENT GURANTEE PROCEDURE

hi,
i am trying to supress the field called payment gurantee procedure in CMR through OBD2.
but
unfortunately i am not able to find the field in customer master data in OBD2 in the relevant accoutn group.
help me on this..
regards,
balajit

Hi,
Go to OBD2 tcode and then double click on the Sales Data that is present under the Field Status Section.
Now, under the select Grouop section double click the Billing option.
Then you see the field "Hedging and credit contr. area", in that select the option Supress.
Note to ensure double click the field "Hedging and credit contr. area", you will find the Payment Guarantee Procedure field.
Regards

Outgoing Payment Approval Procedure - Payment Wizard

Hi,
I was having an issue with the SAP Approval Procedures I was hoping I could get answered.
I have created an Approval Procedure for Outgoing Payments in SAP 8.82 to always require approval.
The approval procedure works fine when I create an Outgoing Payment by going to Banking >> Outgoing Payment >> Outgoing Payment.
If I try to create an Outgoing Payment via the Payment Wizard, it does not go through the approval process.
I have made sure that I have enabled the "Activate Approval Procedures in DI" functionality under General Settings. It still does not do the trick.
Can someone please tell if this is an SAP bug or not? If not a bug, any suggestions as to what I might be doing wrong.
Thanks,
Krishnan

Hi Krishnan,
I believe this is by system design or another word a system limitation. The logic here is: if you are able to run the Payment Wizard, you have authorization already.
A work around may be creating a user alert whenever you have the Payment Wizard run.
Thanks,
Gordon

Payment approval procedure

Dear Guru
Our Management want to do setup for automatic payment procedure for approval
Please provide us the setup in SAP set wise
Regards
Vijay

We have defined the process of released and also assigned Release group in vendor master and
run F110 transaction but system is not asking for release the payment.
Following setup we have done the same
1 Create Workflow Variant for Release for Payment
2 Assign Company Code Workflow Variant for Release for Payment
3 Define Release Approval Groups for Release for Payment
4 Define Release Approval Paths for Release for Payment
5 Assign Release Approval Paths for Release for Payment
But system is not stop payment i.e. not ask for release the payment
Pl suggest the same
Regards
Vijay

Why Payment Guarantee procedure is not appearing in change mode

Hi All,
I am displaying the customer master. The payment guar field is appearing in customer master. But when I go to change mode for the customer master, the payment guar field disappears.
Can somebody throw some light on this.
Note: Pls donot send the configuration details. I have already done the configuration and double checked on the same.
Kind Regards
Chakradhar

Hi Utpal,
Hmm.. this is rather strange. Are you sure it is not entering the SP? Can you try to cancel all operations by changing your SP (make a backup first) to:
-- Return values
declare @error int -- Result (0 for no error)
declare @error_message nvarchar (200) -- Error string to be displayed
select @error = 9999
select @error_message = N'My test error'
-- ADD YOUR CODE HERE
-- Select the return values
select @error, @error_message
Then try to update your document. It should stop you if it is entering. If not then I'd recommend going to SAP support.
Also, if possible, post the code you are using in your SP.
Best regards,
Pedro Magueija

Pyament guarantee

hi,
can any one explain about the <b>payment guarantee</b> procedure in detail
thanx in advance

Hi giri,
Go through this. This is regarding credit card processing and payment gaurantee procedure.
Overview
This document attempts to explain in the brief the credit card processing in SAP.
SAP provides a flexible and secure payment card interface that works with the
software of selected partners that provide merchant processes and clearing house
services. In SAP the credit card processing is integrated with the sales and
distribution module.
Payment card configuration
Much of what is required for credit card processing to work with VISA, Master
Card, and American Express is already set up in SAP.
For all credit card configurations refer to
Define Card Types
Transaction SPRO IMG Sales and Distribution Billing Payment Cards
Here we define the type of cards that can be used in the system. A four-letter
code is given for each card type. E.g. MAST for Master Card, VSAJ for Visa
Japan. A function module for checking the card number is also specified here.
1. Define Card Types
Credit Card Configuration And Processing In SAP
Maintain Card Categories
(a) Define card Categories: Here we specify the card category of the
payment card. With this the system automatically determines the card
category when you enter a card number in master data or sales
documents.
(b) Determine card categories: Here we specify the acceptable number
ranges for different card types. Also card categories are assigned to the
card types. Even though SAP comes with card checking algorithms
(Function Modules) for standard card types this configuration setting
is particularly useful to those cards that do not contain any standard
checking algorithm already set up in SAP.
2. Determine Card Categories
Maintain Payment Card Plan Type
In this step, you assign the payment plan type for payment cards, the payment
card plan type, to all sales document types in which you will be using payment
cards. You cannot process payment cards if you have not made this assignment
The standard system contains payment plan type 03 for processing payment
cards. 3. Show the screen where this assignment is done.
Credit Card Configuration And Processing In SAP
3. Maintain Payment Plan Type
Maintain Blocking Reasons
In this step, you define blocking reasons for payment cards. You enter these in
the payer master record to block cards. The standard system contains blocking
reason 01 for lost cards.
Risk Management for Payment Cards
Transaction SPRO IMG Sales and Distribution Billing Payment Cards
Authorization and settlement Risk Management for payment cards.
Risk Management plays a central role within Sales, providing you with checks
and functions to minimize your credit risk. In addition to letters of credit and
export credit insurance, payment cards are among the payment guarantee forms
that you can use to insure payment for sales order items. SAP comes with predefined
payment forms of guarantee as shown below. Customer can also
maintain other forms of payment suited for their line of business.
Credit Card Configuration And Processing In SAP
Define forms of payment guarantee
3. Define forms of payment guarantee
Maintain payment guarantee procedures
In this step, you define Payment guarantee procedure. These procedure controls,
which form of payment guarantee, are valid for a particular customer, and for a
particular sales document type.
The various settings done under this configuration are
Define payment guarantee procedures
Maintain customer determination procedure
Maintain document determination procedure
Assign sales document types
Determine payment guarantee procedures
Maintain authorization requirements*
Here requirements* are set to tell the system how and when to carry out
authorization when a sales order is saved. SAP comes with two requirements
Form routine 1. Carry out authorization only when the sales document is
complete. The system carries authorization when the order is saved.
Form routine 2. Carry out authorization only when the sales document is
complete, but the authorization for all the complete documents is carried out in
batch.
Additional requirements* can be assigned here as per the business requirements.
*Requirements are ABAP/4 code. Requirements for various functions can be accessed using transaction VOFM
Credit Card Configuration And Processing In SAP
4. Maintain Card Authorization Requirements
Maintain Checking Groups
How and when authorizations are carried out depends on the setting you make in
the customizing for maintain checking group routines.
The three main settings that influence authorization are:
a) Authorization requirements
b) Authorization horizon
c) Preauthorization
There are two settings under this setting.
Define checking group: Here a checking group is defined and the
authorization requirement (described in the previous section), Authorization
horizon (described below) and preauthorization settings are done for this
checking group.
5. Define Checking Group
Credit Card Configuration And Processing In SAP
Here you can see a checking group C1 is defined with the authorization
requirement 902. Checking the pre-authorization tells the system to carryout preauthorization
if the order fulfillment date falls outside the horizon. The
authorization horizon specifies the number of days before the material
availability date, or billing date, that the system is to initiate authorization. If a
sales order is saved within the authorization horizon, the system carries out
authorization immediately. If a sales order is saved before the authorization
horizon comes into effect, the system does not authorize at all, or carries out
preauthorization.
6. Preauthorization Concept
In this example, the system has been set to authorize one day before delivery
creation. The system does not carry out authorization when the order is saved on
Day 0, rather on Day 2. Note that the authorization validity period has been set to
14 days in Customizing IMG Authorization and settlement Specify
authorization validity periods. The transaction will have to be reauthorized if
delivery activities take longer than 14 days.
Assign checking groups: Here the checking groups defined earlier are
assigned to different sales document types as shown 8.
Specify authorization validity periods
Here number of days that an authorization can remain valid for different card
types are maintained. Refer to 9.
Credit Card Configuration And Processing In SAP
8. Assign checking groups
9. Assign validity period for authorization for different card types
Credit Card Configuration And Processing In SAP
Account Determination
Transaction SPRO IMG Sales and Distribution Billing Payment Cards
Authorization and settlement Maintain Clearing House
In the following steps, you set the condition technique for determining
clearinghouse reconciliation accounts for authorization and settlement. The
system uses the entries here to determine the clearing account for the payment
card charges. When settlement is run, the postings in the receivable account for
the payment card will be credited and a consolidated debit will be created and
posted to the clearinghouse account. These accounts are a special type of general
ledger account that is posted from Sales and Distribution.
Here, you maintain:
Maintain field catalog.
Condition tables and the fields that they contain
Access sequences and condition types
Account determination procedures
You then assign these accounts to condition types.
Add to field catalog
Here you maintain the fields that can be used in the condition table. 10.
Shows the transaction to maintain the field catalog.
10. Maintain Field Catalog.
Maintain condition tables
Here condition tables are maintained with fields that are added to the field
catalog. SAP comes pre-configured with two condition tables 4 and 6. Refer
11.
Credit Card Configuration And Processing In SAP
11. Maintain Condition Table
Maintain access sequences
In this step we define an access sequence and link the access sequence with the
condition tables.
Here an access sequence is defined. SAP comes with the access sequence A001.
12. Define Access Sequence
Once the new access sequence is defined, it is linked to the condition tables as
shown in the next screen.
Credit Card Configuration And Processing In SAP
13. Maintain Access For Access Sequence
Selecting an access and clicking fields will display the fields for the selected
access as shown below for access 10 as shown above.
14. Display Access Fields
Maintain condition types
Here condition types are defined and the access sequence to linked to it.
Condition types are contained in account determination procedures and control
which access sequences the system uses to find condition records.
These are The condition tables.
Credit Card Configuration And Processing In SAP
15. Define condition type
Maintain account determination procedure
In this step an account determination procedure is defined and linked to the
condition type (which in turn is linked to the access sequence).
Define account determination procedure
16. Assign account determination procedure.
Here an account determination procedure CC01 is defined and the condition type
CC01 is assigned to it.
Access sequence linked to the condition type
Credit Card Configuration And Processing In SAP
Assign account determination procedures
In this customizing the previously set up account determination procedure is
assigned to different billing documents.
Assign Accounts (G/L)
G/L accounts are assigned here for the combination of Sales organization, Card
type, chart of accounts and condition types as shown in the 17.
17. Assign G/L accounts
Set authorization / settlement control per account
Each G/L account is assigned an authorization and a settlement function module.
The system will read the configuration a call the authorization and settlement
function module during authorization and settlement respectively.
Credit Card Configuration And Processing In SAP
18. Set Authorization and settlement function module
Maintain merchant IDs per account
A merchant may have one or more IDs for each clearinghouse with which it does
business. Here, you assign these different merchant IDs to their related
receivables accounts.
19. Assign Merchant IDs
Credit Card Configuration And Processing In SAP
Authorization and Settlement in SAP
20. Sales Order Cycle With Credit Card Authorization
When an order is placed through the front-end system, the order information,
credit card information, billing information, shipping information is passed to
SAP. SAP processes the order calculates the taxes, the shipping costs and reads
the configuration information settings and executes the function module setup as
described in Fig. 18. The function module formats the data and makes a RFC *
call to the payment application**.
The payment application screens the order for fraud, encrypts the data and
communicates with the third party processor who in turns communicates with
the card association and card issuer.
*RFC (Remote Function Call)
*Payment Application: Middle ware between SAP and third party processor/bank.
Credit Card Configuration And Processing In SAP
The third party processor responds back with the response whether the
transaction is approved or declined or referred.
Note: When any item in the order does not have a confirmed quantity, then
authorization is not carried out for the full amount. A small dollar amount
usually ($1) is used as the authorization amount. During the rescheduling run
the system will check for the material availability. If the material can be
delivered within the horizon date, a full authorization for the order is carried
out.
Approved: When the credit card transaction is approved the systems checks for
the material availability, confirms the material for the ordered quantity and saves
the order.
Declined: The material availability check for the material is not made, and the
order is rejected.
Referred: The order is saved and is blocked for delivery. In this situation is
merchant calls the bank checks for the available credit on the card and a manual
authorization is carried out.
21. Sales Order Entry Screen in SAP
Payment Card
Information
Credit Card Configuration And Processing In SAP
The first line in payment card screen is the card check performed by SAP system,
using the card check algorithm function module as described in 1. And the
remaining lines represent the actual authorizations that are carried out.
22. Payment Card Screen
Path Header Payment Cards.
Settlement
Legally the merchant can charge the credit card after the order has been
completely processed. In SAP this happens after a delivery is created and the
goods has been shipped. In case there is not enough authorization for the order
to be delivered, the system goes out the get the authorization for the remaining
amount.
In SAP settlement is initiated using the transaction FCC1. All the valid
authorization is submitted in a batch to the payment application at scheduled
intervals as specified by the third party processor.
The payment application encrypts this data and communicates with the third
party processor. The third party processor checks if the settlement request has a
valid authorization against it. The third party processor then transfers the fund
from the cardholders bank to the merchant bank.
Mohan
Award points if it helps.

Report to display Average time taken for processing payments".

Hi,
I have been asked to develop a report for "Report to display Average time taken for processing payments".
Could any one guide me technically what are the different tables i need to take to generate the report. Treat this is very urgent. Pls provide sample code too....
Thanks in advance....

Given below is the set up for credit card payment processing:
Set Up Credit Control Areas:
Define Credit Control Area
Transaction: OB45
Tables: T014
Action: Define a credit control area and its associated currency. The Update Group should be 00012. This entry is required so the sales order will calculate the value to authorize
Assign Company Code to Credit Control Area
Transaction: OB38
Tables: T001
Action: Assign a default credit control area for each company code
Define Permitted Credit Control Area for a Company
Code
Transaction:
Tables: T001CM
Action: For each company code enter every credit control area that can be used
Identify Credit Price
Transaction: V/08
Tables: T683S
Action: Towards the end of the pricing procedure, after all pricing and tax determination, create a subtotal line to store the value of the price plus any sales tax. Make the following entries:
Sub to: A
Reqt: 2
AltCTy: 4
Automatic Credit Checking
Transaction: OVA8
Tables: T691F
Action: Select each combination of credit control areas, risk categories and document types for which credit checking should be bypassed. You need to mark the field no Credit Check with the valid number for sales documents.
Set Up Payment Guarantees
Define Forms of Payment Guarantee
Transaction: OVFD
Tables: T691K
Action: R/3 is delivered with form 02 defined for payment cards. Other than the descriptor, the only other entry should be 3 in the column labeled PymtGuaCat
Define Payment Guarantee Procedure
Transaction:
Tables: T691M/T691O
Action: Define a procedure and a description.
Forms of Payment Guarantee and make the following entries Sequential Number 1
Payment Guarantee Form 02
Routine Number   0    Routine Number can be used to validate payment card presence.
Define Customer Payment Guarantee Flag
Transaction:
Tables: T691P
Action: Define a flag to be stored in table.
Create Customer Payment Guarantee = Payment Card Payment Cards (All Customers can use Payment Cards).
Define Sales Document Payment Guarantee Flag
Transaction:
Tables: T691R
Action: Define the flag that will be associated with sales document types that are relevant for payment cards
Assign Sales Document Payment Guarantee Flag
Transaction:
Tables: TVAK
Action: Assign the document flag type the sales documents types that are relevant for payment cards.
Determine Payment Guarantee Procedure
Transaction: OVFJ
Tables: T691U
Action: Combine the Customer flag and the sales document flag to derive the payment guarantee procedure
Payment Card Configuration
Define Card Types
Transaction:
Tables: TVCIN
Action: Create the different card types plus the routine that validates the card for length and prefix (etc)
Visa , Mastercard, American Express, and Discover
Create the following entries for each payment card
AMEX American Express ZCCARD_CHECK_AMEX Month
DC Discover Card ZCCARD_CHECK_DC Month*****
MC Mastercard ZCCARD_CHECK_MC Month
VISA Visa   ZCCARD_CHECK_VISA Month
The Routines can be created based on the original routines delivered by SAP.
*****SAP does not deliver a card check for Discover Card. We created our own routine.
Define Card Categories
Transaction:
Tables: TVCTY
Action: Define the card category to determine if a
payment card is a credit card or a procurement card.
Create the following two entries
Cat Description One Card Additional Data
CC Credit Cards No-check No-check
PC Procurement Cards No-check Check
Determine Card Categories
Transaction:
Tables: TVCTD
Action: For each card category map the account number range to a card category. Multiple ranges are possible for each card category or a masking technique can be used. Get the card number ranges from user community. Below is just a sample of what I am aware are the different types of cards.
Visa Credit Expires in 7 days.
    400000   405500
    405505   405549
    405555   415927
    415929   424603
    424606   427532
    427534   428799
    428900   471699
    471700   499999
Visa Procurement Expires in 7 days.
    405501   405504
    405550   405554
    415928   415928
    424604   424605
    427533   427533
    428800   428899
Mastercard Credit Expires in 30 days
    500000   540499
    540600   554999
    557000   599999
Mastercard Procurement Expires in 30 days
    540500   540599
    555000   556999
American Express Credit Expires in 30 days
    340000   349999
    370000   379999
Discover Card Credit Expires in 30 days
    601100   601199
Set Sales Documents to accept Payment Card Information Transaction:
Tables: TVAK
Action: Review the listing of Sales Document types and enter 03 in the column labeled PT for each type which can accept a payment card
Configuration for Authorization Request
Maintain Authorization Requirements
Transaction: OV9A
Tables: TFRM
Action: Define and activate the abap requirement that determines when an authorization is sent. Note that the following tables are available to be used in the abap requirement (VBAK, VBAP, VBKD, VBUK, and VBUP).
Define Checking Group
Transaction:
Tables: CCPGA
Action: Define a checking group and enter the
description. Then follow the below guidelines for the remaining fields to be filled.
AuthReq Routine 901 is set here.
PreAu If checked R/3 will request an authorization for a .01 and the authorization will be flagged as such. (Insight does not use pre-authorization check).
A horizon This is the days in the future SAP will use to determine the value to authorize
(Insight does not use auth horizon period).
Valid You will get warning message if the payment card is expiring within 30 days of order entry date.
Assign Checking Group to Sales Document
Transaction:
Tables: TVAK
Action: Assign the checking group to the sales order types relevant for payment cards
Define Authorization Validity Periods
Transaction:
Tables: TVCIN
Action: For each card type enter the authorization validity period in days.
AMEX American Express 30
DC Discover card 30
MC Master card 30
VISA Visa   7
Configuration for clearing houses
Create new General Ledger Accounts
Transaction: FS01
Tables:
Action: Two General Ledger accounts need to be created for each payment card type. One for A/R reconciliation purposes and one for credit card clearing.
Maintain Condition Types
Transaction: OV85
Tables: T685
Action: Define a condition type for account determination and assign it to access sequence A001
Define account determination procedure
Transaction: OV86
Tables: T683 / T683S
Action: Define procedure name and select the procedure for control. Enter the condition type defined in the previous step.
Assign account determination procedure
Transaction:
Tables:
Action: Determine which billing type we are using for payment card process.
Authorization and Settlement Control
Transaction:
Tables: TCCAA
Action: Define the general ledger accounts for reconciliation and clearing and assign the function modules for authorization and settlement along with the proper RFC destinations for each.
Enter Merchant IDs
Transaction:
Tables: TCCM
Action: Create the merchant ids that the company uses to process payment cards
Assign merchant ids
Transaction:
Tables: TCCAA
Action: Enter the merchant ids with each clearinghouse account

Sales order block for MRP run when the Customer payment terms is in Advance

My client needs to block some sales order for MRP which customer payment term is advance. But it should be based on the customer payments terms (In case of Advance). After getting his advance amount, we would be release it and it also be consider for MRP.
Option 1.Status profile this concept is will controlled by sales document controls VOV8 not by customer's payment term Advance
Option 2: In CMR sales area Billing Document tab by using payment guarantee procedure and in VOV8 in billing tab Payment guaramtee procedure by using this setting , i am getting a pop up message" No Finanical document assigned" in sales order when u try to save. Now sales order is blocked for delivery but not MRP run.
i am to ask the abaper to develop "here in the information box we will maintained required text say example u201C customeru2019s Payment term is in advance please check the reason for rejection number u201Csay ex: 13u201D: advance " after this is happen go to change mode of sales order put reason for rejecation" now MRP run will not generate the requirement for the sales order.
for Undo these this flow :
Va02 : remove the reason for rejection keep it in Blank
VKM3 : release the sales order.
Options 3: Development
Kindly suggest me the second options is only alternative for solving this issue but really i m not used specific feilds to solving this issue.

Cleint is not using the field in CMR Payment granatee , i gone for user-exit and closed this issue

Payment Gauranteed Procedure

Similar Messages

Maybe you are looking for