Configuring SAP Credit management interfaces in PI 7.0

Hi all,
I am working on PI 7.0 instance and have an issue while trying to connect Accounts receivable accounting with SAP Credit Management.
Did anybody configure this kind of interfaces (Credit cOMMITMENT & Credit Payment) so that they could be integrated with PI?
If so, could you please tell me the steps to configure the mappings and CCs in IR and ID?
i am following SAP Credit mngmnt config guide, but there is no info regarding this.
TCODES are: UKM_TRANSFER_ITEM & UKM_TRANSFER_VECTOR
Best regards,
David

try sapsr3.<table> instead of sap<sid>
SAPSR3 is the schema now. Once lock is removed , try to login with sap*/ddic with master password which you gave while installing.
Thanks
Prince Jose

Similar Messages

ECredit vs SAP Credit Management

SAP Experts,
Has anyone ever used eCredit? I am interested in understanding the functionality it provides vs. SAP Credit management and any gap, interface issues.
Thanks in advance.

Hi,
SAP Credit Management module basically checks the credit status and whether an Order / Delivery needs to be blocked / processed. This settings can be configured as per the Business requirement.
eCredit is a third party tool which basically gives a credit worthiness of a Customer. We can get information through an incoming interface and we can send update information toeCredit with an external interface.
For business transactions SAP Credit Management should be implemented which faciliates real time credit check.
Thanks
Murali.

DNB integration with FSCM SAP Credit management

Hi,
Any body worked on or integrated DNB with FSCM SAP Credit management ? if it is please share some information /document on integration.
Thx
DD

Hi Ankur
You can integrate with DNB either online or batch mode .
.Online mode
    In this mode, a request is sent from FSCM to DNB for credit data. A response is sent by the DNB synchronously, for the request initiated from FSCM.
    Following was done to implement this. Middle ware (java based) created a web service and in FSCM we created a client proxy to consume the web service.
To initiate the request from FSCM, we called a web service method using a custom program passing the relevant information like agency name, customer name etc.
To call the web service method through the proxy, we had to pass the port name in the proxy call. The URL for the web service was configured in the port (transaction LPCONFIG). Middle ware got the request and in real time passed it to the DNB using integration technique   The DNB sent response back to Middle Ware in real time and Middle ware passed it back to FSCM using the same web service used for the request from FSCM.
. Batch mode -
In this mode, there was no request from FSCM side. Middle ware will aggregate credit data from DNB on periodic basis and dump the data as xml files in FSCM application server. A batch job (custom program) will be    scheduled in FSCM to process the xml files provided by Middle ware and update credit data from agencies in FSCM.
Thanks
Rajesh Kanamarlapudi

SAP Inventory management interface with Third party Warehouse System

Hi Experts,
Need your input for designing the SAP solution with existing Third party warehouse system ( Exacta ):-
SAP ERP will be implemented for all locations of Client ( SAP MM, FI, PS , HR etc ).The Client has 10 distribution centres which are on Exacta Warehouse systems and will be linked with SAP Inventory management system.
The way it will work - Goods receipt will always happen in SAP for all locations and then interface needs to Trigger subsequent Putaway activities at Exacta Ware house ( third party warehouse system) for those 10 locations.
Goods Issue for these locations will happen from Exacta and then update will be posted in SAP via interface.
All locations will be created as Plant /Storage locations in SAP.
Need your inputs what special configurations need to happen in SAP for those locations so that goods receipt in SAP can trigger putaway activities in Exacta system .
Do we need to do configuration for decentralised Warehouse in SAP for handling this?
Pl. give your inputs based on your past experience where you handled such scenarios via interface with SAP Inventory management and legacy warehouse systems.
Thanks for quick response on this.
Regards,
Krish

Krish
This is a std business process where clients have used their existing warehousing systems but implemented SAP forother functions such as Order entry, inventory mgmt and procurement, financials.
The typical interface that needs to happen is
1. Sales order ( and or delivery)
2. Invetory needs to be passed to the WH. Typically people send it when SAP GR takes place.
3. When WH system does picking, it sends signal to SAP which then does PGI for the sales order delivery and that takes the stock out of the system.
Material master has to be transferred or mapped between two systems. Also, other elements need to be mapped between two systems.
The way I have seen this happening is :
you have an output on the SAP GR process. That creates an idoc to the WH system. Based on the capabilities of the WH system, it then does appropriate actions in the system.
Many times, middlewares are used to translate/ map the data between SAP and the WH systems.
So system wise, there is ALE setup that needs to take place for IDOC creations.
Configuration and coding is required for the output type and the program behind it. There are several std FUnction Modules that can be used for this.
Hope this helps.
Mankai

SAP inventory management interface with third party warehouse

Hi Experts,
Need your input for designing the SAP solution with existing Third party warehouse system ( Exacta ):-
SAP ERP will be implemented for all locations of Client ( SAP MM, FI, PS , HR etc ).The Client has 10 distribution centres which are on Exacta Warehouse systems and will be linked with SAP Inventory management system.
The way it will work - Goods receipt will always happen in SAP for all locations and then interface needs to Trigger subsequent Putaway activities at Exacta Ware house ( third party warehouse system) for those 10 locations.
Goods Issue for these locations will happen from Exacta and then update will be posted in SAP via interface.
All locations will be created as Plant /Storage locations in SAP.
Need your inputs what special configurations need to happen in SAP for those locations so that goods receipt in SAP can trigger putaway activities in Exacta system .
Do we need to do configuration for decentralised Warehouse in SAP for handling this?
Pl. give your inputs based on your past experience where you handled such scenarios via interface with SAP Inventory management and legacy warehouse systems.
Thanks for quick response on this.
Regards,
Krish
Edited by: krishnendu Bhowmik on Nov 24, 2009 4:22 PM

Hi experts,
Any inputs on this .
Thanks again,
Krish

How do we configure in credit management

Hi Gurus,
My client have a scenario like particular products (Some Mateials) the customer wants
business dont give any credit limit for that products. Like certain period of time like 45 days payment of terms once he crosses 45 days the system should block the sales orders with the settings. Where do we maintain particular products with payment terms. where do we configure for that particular products for that particular customers. in credit management.
Thanks & Regards
Points will be rewarded.

Hi,
Define Payment Terms,refer to this website
http://www.saptechies.com/payment-terms-plus-no-of-daysmonths-2/
In payment terms, there is one payment term 001-pay immediately, for 45 days there is another payment term, you can use that.In fact, you can use sap standard payment terms.
Regarding credit credit management, a company gives its customers credit for certain period of time.If the credit exceeds,
the system shows a warning message or error message to the user that credit limit has excedded. I suggest you configure only warning message, for error message, you have to go for configuration change.
For Credit Management, refer to below weblinks.
http://www.sap-img.com/sap-sd/credit-management.htm - For SD & FI
http://www.sap-basis-abap.com/sapfj006.htm - For FI
Please let me know if you need more information.
Assign points if useful.
Regards
Sridhar M

Configuration SAP Solution Manager TCode-SOLMAN_SETUP Initial Configuration

Hi,
I am running the TCode: Solman_Setup for Basic Configuration in Solman 7.0 EHP1.
In "Initial Configuration" -> Technical Configuration after clicking Configure button facing following error. Pls Suggest.
System SM1 does not exist & E::000
Regards
Praveen K

E::000 basically means that the system is trying to show an error message "000" from a specific error message set.This problem is caused by a program error. If the authorization check fails, no relevant error message is displayed.
have you created any system by the name SM1 in SMSY?
Regards,
Rajeev

SAP Credit Management (FSCM 2.0) - Adding addtional informations

Hi Friends,
I am trying to add additional information by using BAPI : BAPI_BUPA_FS_BPADDITION_ADD .
But this works only when the Diff Val ( BUT100 Table ) and the Criteria ( BP3100 Table ) which i am passing in additional info internal table to BAPI
is same i.e 'Blank".
Scenario :
Suppose that i am adding additional Information with Criteria : ZLIN the Bapi executes fine but during the Commit it gives DUMP , the error message during DUMP is as follows : No diff. criterion-dependent BP role with differentiation ZLIN exist.
What i observed when i am saving thru standard transaction code UKM_BP is that BUT100 has partner and role normal values , But when BP3100 has a new entry with criteria with value "ZLIN" the entry in BUT100 gets updated with Diff Value : ZLIN.
Does anyone know how to solve this problem of table update of BUT100 through BAPI or Method Call which is happening internally before commit in the standard tcode.
Also can i use any methods of class CL_UKM_BUSINESS_PARTNER to handle the update of additional Information .
Please reply if anyone has found any solution. This is a bit urgent.
Regards,
Navin Fernandes.

Hi,
Below is the code i have added in the method FILL_FIELDS.
method IF_EX_UKM_BP_ADD_FIELDS~FILL_FIELDS.
DATA: go_facade        TYPE REF TO cl_ukm_facade,
          go_calculator    TYPE REF TO if_ukm_calculator,
          go_bupa_factory TYPE REF TO cl_ukm_bupa_factory,
          go_partner       TYPE REF TO cl_ukm_business_partner.
DATA: go_account       TYPE REF TO cl_ukm_account.
DATA: ls_vector TYPE ukm_s_bp_vector.
data: lt_vECTOR_IT type UKM_TS_BP_VECTOR_IT,
        ls_vector_it like line of lt_vECTOR_IT.
data: l_segment type ukmbp_vector_it-credit_sgmnt.
go_facade   = cl_ukm_facade=>create(
                  i_activity = cl_ukm_cnst_eventing=>bp_maintenance ).
go_bupa_factory = go_facade->get_bupa_factory( ).
l_segment = '0000'.
use Segment 0000.
CALL METHOD go_bupa_factory->get_credit_account
    EXPORTING
      i_partner         = i_partner
      i_credit_sgmnt    = l_segment
    RECEIVING
      ro_credit_account = go_account.
CALL METHOD go_account->get_bp_vector
    IMPORTING
      es_bp_vector = ls_vector.
     ET_BP_VECTOR_IT = lt_vECTOR_IT.
if not ls_vector is initial.
    MOVE-CORRESPONDING ls_vector TO es_bp_customer_extension.
    exit.
Endif.
endmethod.
and i did not use the remaining two methods in the BADI, i used this method to add the parameters in the formula builder.
Thanks & Regards,
Venu Gudala.

Credit Managment : Profile tab is not visible in BP

Hi All ,
I am working on FSCM credit managment project.
For FSCM credit managment :
I have activated the Badi : activation of SAP credit managment (Interface Set Active and FI_AR_Upadte mode)
1)Set Active
E_ACTIVE_FLAG = 'X' .
E_ERP2005 = 'X'
2)FI_AR_Upadte mode
E_DIRECT_UPDATE = 'X'.
But when I am selecting the Bussiness partner under (SAP credit managment role ).Profile tab is not visible .
Please help me out .
Regards
Rahul

Hi,
Pls check note 956054 and see if you have set up the business partner the correct way. This is the basis.
Rgds,
Richard

Configuration of SAP Organization Charting Interface.

Hi Gurus,
Can any one guide me how to configure SAP Organization Charting Interface using ABAP Webdynpro.
Regs,
Brahma

Hi
What is the Org charting tool that you want to implement.
For SAP we have NAKISA an org charting tool which is an authorized tool for SAP.
make an FS and the ABAP person will do the interface.
R K

Credit Management Process based on Terms of Payment.

Hi All,
My Client wants to use SAP Credit Managment Process. The SAP is currently being used but without Credit Management. As per my initial discussion I have enclosed the requirments below. Your Kind Help will be highly appreciated.
1.     The Process has to be implemented in a 2 Step Process.
2.     The Initial Requirement is based on Terms of Payment. If the Number of Days is Overdue for the Invoice for a particular Customer, the system should issue a warning message (in the Form of Mail or any other way) which can be shown as evidence to the Customer for collection of Payment so that further Sales Transactions can take place.
(Is there the standard Process in Credit Management based on Terms of Payment)
3.     In the next step Value Base Credit Check has to be implemented. The Value will be set for a particular Customer in Credit Master. When the Sales Order is raised and if the Credit Limit is exceeded the System should issue the warning message. Based on the Warning Message Issued an email should triggered to the particular person in Finance that the Credit Limit for a particular person has been exceeded and Credit Limit needs to be increased.
Thanks & Regards,
Sam.

Dear Mr F Farooq,
1. The Process has to be implemented in a 2 Step Process.
Do the following configurations for credit management :
Refer the following link.
http://wiki.sdn.sap.com/wiki/display/ERPLO/CreditManagementConfigaration
2. The Initial Requirement is based on Terms of Payment. If the Number of Days is Overdue for the Invoice for a particular Customer, the system should issue a warning message (in the Form of Mail or any other way) which can be shown as evidence to the Customer for collection of Payment so that further Sales Transactions can take place.
(Is there the standard Process in Credit Management based on Terms of Payment)
Now for this requirement, since different billing documents for the same customer can have different payment terms (whcih means different billing will be due on different date) , please make the following changes in OVA8
Check for 'oldest open item'
Now follow my reply in the below thread.
Sales order to be blocked based on customer payment terms and credit limit
You can use WORKFLOW to trigger mail when such a message is triggered in the sales order , due to credit check.
Ask your ABAP-er for details on workflow.
3. In the next step Value Base Credit Check has to be implemented. The Value will be set for a particular Customer in Credit Master. When the Sales Order is raised and if the Credit Limit is exceeded the System should issue the warning message. Based on the Warning Message Issued an email should triggered to the particular person in Finance that the Credit Limit for a particular person has been exceeded and Credit Limit needs to be increased.
Just configure according to the thread given for 1st POINT.
CHECK FOR DYNAMIC and set reaction as 'C' and check STATUS /BLOCK.
Maintain the credit limit in the FD32.
Now when the sales order value exceeds the credit limit , a message will be triggered.
Use the concept of WORKFLOW to create mail based on this message .
When the user gets mail, he can maintain the new credit limit in FD32 and release the document for delivery/billing in VKM3.
Revert back if there is any issues.
Thanks & Regards,
Hegal K Charles
Edited by: Hegal . K . Charles on Aug 7, 2011 1:19 AM

XI and Credit Management in FSCM 6.0

Hello,
We have ERP2005 with FSCM and want to use the Credit Commitment interface ( http://help.sap.com/erp2005_ehp_01/helpdata/en/43/2a1c518e5f601fe10000000a422035/frameset.htm ) to pass FI-AR data to SAP Credit Management via XI. The sender is the FI-AR system and the receiver is the SAP Credit Management system Both FI-AR and FSCM are on the same ERP2005 system and XI is on a seperate system.
I have downloaded the XI content for the the intefaces CreditCommitmentNotification_Out and CreditCommitmentNotification_In and set up the configurartion so messages come out of ERP and the determined receiver is the same ERP system but my problem is with the receiver communication channel. The SAP help link referenced above says I should be using the communication channel XIChannel. Can someone help me and tell me what type of communication channel this is and what I have to do set it up please.
Thanks in advance for your help.
Pete

Felipe,
Thanks for the info it solved the problem and the interface works now. For future reference in case anyone has the same problem the scenario is as follows
Sender                  = ERP (FI module)
Sender interface     = http://sap.com/xi/PI/FIN/Operational/Global
Sender namespace = CreditCommitmentNotification_Out
Receiver = ERP (FSCM)
Receiver interface     = CreditCommitmentNotification_In
Receiver namespace = http://sap.com/xi/FSCM/Global
No interface mapping is required just set up the receiver determination with receiver determination to use a receiver communication channel of type XI.
Thanks,
Pete

Credit management urgent

Dear sap gurus,
after implementing credit management in middle or not from beginning and if you want to have the history a particular customer updated in LIS or if we want to know about his credit exposure.
What should be done.Kindly help me.
regards,

How To Do Configuration For Credit Management
Credit and risk management takes place in the credit control area. According to your corporate requirements, you can implement credit management that is centralized, decentralized, or somewhere in between.
An organizational unit that represents the area where customer credit is awarded and monitored. This organizational unit can either be a single or several company codes, if credit control is performed across several company codes. One credit control area contains credit control information for each customer.
For example, if your credit management is centralized, you can define one credit control area for all of your company codes.
If, on the other hand, your credit policy requires decentralized credit management, you can define credit control areas for each company code or each group of company codes.
Credit limits and credit exposure are managed at both credit control area and customer level. You set up credit control areas and other data related to credit management in Customizing for Financial Accounting. The implementation guide is under Enterprise Structure -> Definition or Assignment -> Financial Accounting and then Maintain credit control area. You assign customers to specific credit control areas and specify the appropriate credit limits in the customer master record.
Settings for determining the credit control area of a document. The settings of items 1 - 4 are taken into account according to their priority. The credit control area found is stored in field VBAK-KKBER.
1. Transaction OB38
Check which credit control area is assigned to the company code.
Company code:
Credit control area:
2. Transaction OVFL
Check which credit control area is assigned to the sales area.
Sales area:
Credit control area:
3. Transaction XD02 or VD02
Check which credit control area is assigned to the payer.
Payer:
Credit control area:
4. Transaction SE37
Is user exit EXIT_SAPV45K_001 being used?
5. Transaction OBZK
For the settings under items 2 - 4, field "All company codes" must be marked in Transaction
OB45, or the credit control area must be entered under the relevant company code in table
T001CM of the credit control areas allowed.
Company code:
Credit control areas allowed:
6. Settings for the credit checks
7. Transaction OVAK
Which settings do exist for the sales document type used?
Sales document:
Check credit:
Credit group:
8. Transaction OVAD
Which settings do exist for the delivery type used?
Delivery type:
Credit group for delivery:
Credit group for goods issue:
9. Transaction OB01
Credit management/Change risk category
Definition of the risk category for each credit control area. This risk category can be
assigned to a credit account by using Transaction FD32.
10. Transaction OVA8
Here, the individual credit checks for key fields
o credit control area
o risk category
o credit group are set. Take these key fields from the above settings and go to the detail
screen. In particular, check whether fields "Reaction" and "Status/block" are set
correctly. To carry out follow-up actions in case of a credit block, the credit check
status must be set (field "Status/block").
11. Transaction FD32
Credit master data for the payer of the relevant document.
Credit account:
Credit limit:
Risk category:
Currency:
12. Settings for updating the credit values Update of the credit values is required for the limit
check (static or dynamic credit limit check).
13. Transaction OVA7
Update of the credit value is active for the corresponding item type if the check box is marked. This field corresponds to
field "Active receivable" in Transaction VOV7.
Item type:
Active receivable:
14. Transaction V/08, Pricing
In the pricing procedure used for pricing, subtotal "A" must be entered in a line for
determining the credit value (mark the pricing procedure and doubleclick on "Control").
Usually, the net value plus taxes is used. This way the system is determined to use this
subtotal for credit pricing. The credit price is stored in field VBAP-CMPRE and used for
update and credit check.
You can find the used pricing procedure of the order under "Item -> Condition -> Analysis".
Pricing procedure:
Line with subtotal = 'A':
15. Transaction OB45
Which update group (field "Update") do you use in the relevant credit control area? The
default setting is "12". If you use another update group, check whether this is fine with
you. If you open an OSS message, please tell us the alternative update group.
Credit control area:
Update:
16. Transaction OMO1
Which kind of update did you choose for structure S066?
In any case, "Synchronous update (1)" has to be chosen as the kind of update.
All other settings will lead to errors.
Difference Between Simple and Automatic Credit Check Types
In automatic check, difference between static and dynamic checks.
SIMPLE CREDIT CHECK : Tr.Code - FD32
It Considers the Doc.Value + Open Items.
Doc.Value : Sales Order Has been saved but not delivered
Open Item : Sales Order has been saved , Delivered, Billed & Transfered to FI, but not received the payment from the customer.
Eg: Customer Credit Limit is Rs.1,00,000/-
Suppose Doc.Value + Open Item Value is Rs.1,10,000/-
Here credit limit exceeds then system reacts.
Options : A) Warning Message
B) Error Message (Sales Order won't be saved)
C) Error Message with Delivery Block
AUTOMATIC CREDIT CHECK : Give extra credit facilities to the particular customer.
STATIC CREDIT LIMIT DETERMINATION :Checking Group + Risk Catageory + Credit Control Area.
A) Credit Checking Groups : Types of Checking Groups.
01) Sales
02) Deliveries
03) Goods Issue
At all the above 3 levels orders can be blocked.
B) Risk Catageory : Based on the risk catageories company decide how much credit has to give to the customer.
HIGH RISK (0001) : LOW CREDIT
LOW RISK (0002) : MORE CREDIT
MEDIUM RISK(0003) : Average Credit
Static Credit Check it checks all these doc value & check with the credit limit
1) Open Doc.Value / Sales Order Value : Which is save but not delievered
2) Open Delivery Doc.Value : Which is delivered but not billed
3) Open Billing Doc.Value : Which is billed but not posted to FI
4) Open Item : Which is transfered to FI but not received from the customer.
DYNAMIC CREDIT CHECK : 1) Open Doc
2) Open Delivery
3) Open Billing
4) Open Items
5) Horizon Period = Eg.3Months
Here the System will not consider the above 1,2,3& 4 values for the lost 3 months
Then assign the Sales Doc & Del Documents.
Sales Doc.Type(OR) + credit Check(0) + Credit Group (01)
Credit Limit Check for Delivery Type : Del.Type (LF) + Del Credit
Group (02) + Goods Issue Credit Group (03)
Set Up for Credit Card Payment Processing
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 u201800012u2019. 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: u201CAu201D
Reqt: u201C2u201D
AltCTy: u201C4u201D
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 u201Cno Credit Checku201D 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 u201C02u201D defined for payment cards. Other than the descriptor, the only other entry should be u201C3u201D in the column labeled u201CPymtGuaCatu201D
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 u201C1u201D
Payment Guarantee Form u201C02u201D
Routine Number u201C0u201D 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 = u201CPayment Card Payment Cards (All Customers can use Payment Cards)u201D.
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 (etcu2026)
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 u201C03u201D in the column labeled u201CPTu201D 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 u201CA001u201D
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 IDu2019s
Transaction:
Tables: TCCM
Action: Create the merchant idu2019s that the company uses to process payment cards
Assign merchant idu2019s
Transaction:
Tables: TCCAA
Action: Enter the merchant idu2019s with each clearinghouse account
Reward points if useful.
Regards,
Anbu

Connection between SD and FSCM credit management

Hi expert,
   Right now, i used SAP ERP 6.0 and i want to implement FSCM credit management in the same system.
   I already done for configuration in SPRO-> Integration with Sales and Distribution
                                          implemented the following BADI -> BAdI: Activation of SAP Credit Management
                              BAdI: Fill Line Items for Credit Exposure Update and BAdI: Connection of SD to SAP Credit Management
Once i created sales order via t-code VA01, i got the error message
                            Error in XI: Technical Error
                                   Message no. UKM_PI008
Please kindly advice. I'm not sure we need to set up XI or not and how to set up.
Best Regards,
jenny

Dear Venu,
In Credit management configuration I configured everything but in that I have question related to XI.
For SAP FSCM Credit management do we need to activate XI ??? we have SAP FSCM credit management and FI- AR credit management in same system.
I activated the BAdI which is used to activate the SAP FSCM Credit management, After activating this BAdI i created sales order , after i input sold to party , i got the error message as above message.
Menu path for that BAdI is
SPRO -> Financial Supply Chain Management -> Credit Management -> Integration with Accounts Receivable Accounting and Sales and Distribution -> Integration with Sales and Distribution -> BAdI: Activation of SAP Credit Management
SPRO -> Financial Supply Chain Management -> Credit Management -> Integration with Accounts Receivable Accounting and Sales and Distribution -> Integration with Sales and Distribution -> Customer Enhancements -> BAdI: Connection of SD to SAP Credit Management
If you have any information related to this , please provide it to me .
Best Regards,
Jenny

Warnings in FSCM Credit Management for negative credit check.

Hello,
I am implementing FSCM Credit Management. I have below requirement.
At the time of creation of sales order, if credit limit is exceeded then only warnings are required, Sales order should not go in the block (as available in earlier SAP AR Credit Management)
Is this also possible in FSCM Credit Management ? As in the configuration for credit rules, in the log , only extensive log, no log & error message is supported. Follow up event also has option of blocking business partner or workflow once credit check is performed & if it is negative.
Thanks in advance.
Abhishek Govilkar

Yes it is possible thru define autometic Credit Control ( OVA8).
In the " View for maintainace of Autometic Credit control" screen under the "checks tab"
select check box - sap credit management
reaction - c
status/block - unchek
Regards
Rinku Bhowal

Configuring SAP Credit management interfaces in PI 7.0

Similar Messages

Maybe you are looking for