In this Post we will see the other badi's useful for self service procurement
This badi is used to determine your own G/L Account. If we see standard there is a config. In Standard SRM System the G/L account is determined by configuration.
If we see the configuration under SRM Server->Cross-Application Basic Settings ->Account Assignment->Define G/L account for product category and Account Assignment Category
This is the config where we need to maintain the G/L account for a particular Product Category.So this badi can be used to determine your own cirteria for the G/L determination based upon the product category. This badi has only one method called " DETERMINE_ACCOUNT", This method has two parameters
As the name suggests that it determines the logical system. So this badi is used to define your own criteria for determining of Backend sytem and company code. If we see standard there is a config to maintain this. Under SRM SERVER-> Technical Basic Settings->Define Backend System for Product category
DETERMINE_LOGSYS-> Use this method to determine the backend system for the Shopping Cart
CONTRACT_LOGSYS_DETERMINE-> Use this method to determine backend sytem for the contract.
This badi is a filter dependent badi which is used to do changes to the document.This badi has following mehtods
BBP_BID_CHANGE
BBP_AUC_CHANGE
BBP_QUOT_CHANGE
BBP_CONF_CHANGE
BBP_SC_CHANGE
BBP_PO_CHANGE
BBP_IV_CHANGE
BBP_CTR_CHANGE
BBP_SUSPCO_CHANGE
BBP_SUSPO_CHANGE
BBP_SUSASN_CHANGE
BBP_SUSINV_CHANGE
BBP_PCO_CHANGE
BBP_SUSCF_CHANGE
You can use this badi and implement it for the above object types.
This badi also is a Filter dependent badi, This badi is used basically to update/save user data while saving the document. This badi has one method called "BBP_DOC_SAVE"
This is a Filter Dependent badi. There is a config for the determinaiton of the object type.
Path: SRM Server->Cross Applicaiton Basic Settings->Define Objects in Backned System . By implemnting this badi you can define you own cirteria for determination of the object type. This badi has only one method "DETERMINE_TARGET_OBJECT_TYPES"
This badi is a Filter Depedent badi, This badi is implemented when you are defining the n-step approval flow for the Shopping carts. This Badi has two methods
GET_REMAING_APPROVERS -Determines the Approvers and the Approval Steps
SET_APPROVAL_DESCRIPTION- Allows (Lang.Dependent) Setting of Step Description
Badi Name: BBP_DETERMINE_ACCT
Purpose To determine the G/L Account of your defined criteriaThis badi is used to determine your own G/L Account. If we see standard there is a config. In Standard SRM System the G/L account is determined by configuration.
If we see the configuration under SRM Server->Cross-Application Basic Settings ->Account Assignment->Define G/L account for product category and Account Assignment Category
- ITEM_DATA
- ACCT_DATA
Badi Name: BBP_DETERMINE_LOGSYS
Purpose: To determint backend system and company code based upon cirteriaAs the name suggests that it determines the logical system. So this badi is used to define your own criteria for determining of Backend sytem and company code. If we see standard there is a config to maintain this. Under SRM SERVER-> Technical Basic Settings->Define Backend System for Product category
We can overwrite this by using own criteria and that is being passed to this badi for determination of Logical system
This badi has two methodsDETERMINE_LOGSYS-> Use this method to determine the backend system for the Shopping Cart
CONTRACT_LOGSYS_DETERMINE-> Use this method to determine backend sytem for the contract.
Badi: BBP_DOC_CHANGE_BADI
Purpose:Making changes to the documentThis badi is a filter dependent badi which is used to do changes to the document.This badi has following mehtods
BBP_BID_CHANGE
BBP_AUC_CHANGE
BBP_QUOT_CHANGE
BBP_CONF_CHANGE
BBP_SC_CHANGE
BBP_PO_CHANGE
BBP_IV_CHANGE
BBP_CTR_CHANGE
BBP_SUSPCO_CHANGE
BBP_SUSPO_CHANGE
BBP_SUSASN_CHANGE
BBP_SUSINV_CHANGE
BBP_PCO_CHANGE
BBP_SUSCF_CHANGE
You can use this badi and implement it for the above object types.
Badi: BBP_DOC_SAVE_BADI
Purpose: To update Data at the time of saving documentThis badi also is a Filter dependent badi, This badi is used basically to update/save user data while saving the document. This badi has one method called "BBP_DOC_SAVE"
Badi : BBP_TARGET_OBJTYPE
Purpose: To determine backend target system by defining user criteria.This is a Filter Dependent badi. There is a config for the determinaiton of the object type.
Path: SRM Server->Cross Applicaiton Basic Settings->Define Objects in Backned System . By implemnting this badi you can define you own cirteria for determination of the object type. This badi has only one method "DETERMINE_TARGET_OBJECT_TYPES"
Badi:BBP_WFL_APPROV_BADI
Purpose: To implement n-Step approval workflowThis badi is a Filter Depedent badi, This badi is implemented when you are defining the n-step approval flow for the Shopping carts. This Badi has two methods
GET_REMAING_APPROVERS -Determines the Approvers and the Approval Steps
SET_APPROVAL_DESCRIPTION- Allows (Lang.Dependent) Setting of Step Description
No comments:
Post a Comment