'Add Approver' is inactive for SRM contracts

Dear colleagues,
We have deal with SRM 5.5. The point is that the button 'Add Approver' is inactive for 'Approval Preview'.
This issue regarding SRM contracts. Does anybody know how to activate usage of "add approver" during approvement of a contract.
Many thanks in advance for your help.
Kind regards,
Grygoriy
P/S
I've had a look at notice 'ADD Approver/Reviewer buttons are disabled' by N M Poojari ( ADD Approver/Reviewer buttons are disabled), unfortunately, author didn't point to solution of his problem. So, I'll appreciate more detailed plan of actions.

Thanks, Siobhan, for your reply.
However, the problem was caused by my attempt to to do the following steps with a wrong WF (instead standart workflow for contracts (WS14000148) we use Z-flow) :
PFTC -> Select workflow template -> workflow you are using -> Display -> Additional data ->
Agent Assignment -> Maintain -> Attributes -> Select radio button
'General Task'. -> The problem is solved
Yours faithfully,
Grygoriy Gavrylyuk

Similar Messages

Add Approver button disabled for PO in sap srm when GR and IR are already posted

Hello Gurus,
One of my user has edited an old PO for which the GR and IR has already been posted in backend. Now the reason for editing was to change the expected value for 3 item and he changed the value the approver is still blank as for old PO's there was no approval required but later on the whole scenario changed and based on total value the approvers are decided now. But for this PO still its not showing the appovers and also the add approver button is disabled. Is there any way to enable the Add approver button. Also please let me know whether addition of approver is allowed after the GR and IR are posted in backend.
Thanks
Gaurav Gautam

Solved.
In Control Actions -> Configure Control of Actions on Header Level, it's not neccessary put the subtype equal to 0.

Workflow for SRM (contracts and purchase)

Hi Gurus..could you send me this documentation of Workflow
(configuration guide). I have to activate the N-Steps approval fo contracts and purchase order for SRM 5.0.
thanks,
Gustavo Nogueira

Hi,
See the foll links;
http://help.sap.com/saphelp_srm50/helpdata/en/8b/4fa9585db211d2b404006094b92d37/content.htm
http://help.sap.com/saphelp_srm40/helpdata/en/5a/c5173f5ff48443e10000000a114084/content.htm
http://help.sap.com/saphelp_srm40/helpdata/en/26/0f8b41ed891609e10000000a155106/content.htm
BR,
Disha.
Do reward points for useful answers.

Add Approver button disabled in SRM Shopping cart

Hello,
We have activated 2 level PC workflow. However we are facing issue that Add Approver button is not enabled.
Could anyone please advise.
Thank you
Ritesh

Hi Ritesh,
On the face of it,I have couple of points for you to check it out.
1.
Please check the agent assignment at the header level of the workflow.
Go to transaction PFTC -> Select workflow template -> 14000133 (or
whichever workflow you are using) -> Display -> Additional data ->
Agent Assignment -> Maintain -> Attributes -> Select radio button
'General Task' .. or instead of everybody being able to make changes
you can set the agent assignment of the workflow at role level.
Please also review note 581191.
2.Check if this button is not visible or not for all the roles.
3.Check any portal enhancements or Metadata config to make it display.
Thanks
Balaji

Service Breakdown for SRM Contracts

Hi Folks!
We are using SRM 5.0 and R/3 4.0 for Contract Management scenario. We are evaluating options creating Contracts for services. In R/3 I understand that we can maintain the service breakdown while creating the contracts for services.
Is it possible to maintain service breakdown in SRM as well, if no any suggestions or resources that explain how we can map this scenario in SRM.
Regds
Amith

Hi Amith,
This functionality is not possible in SRM as of now.
Please refer this note in that regard 505030 even though it is meant for External Requirements as service which may give you a better understanding on this issue.
If you can explain what exactly you want to have in the service contract we could help you further.
Award points for helpful answers.
Rgds,
Teja

SRM and MDM for material master in SRM contracts for multiple R/3

Dear all,
my question is:
We are implementing SRM 4.0 in classic scenario with multiple R/3 back-end and we want to set-up Global Outline Agreements in SRM in a multi-backend environment where the Material Master are not harmonized.
We heard that MDM and COntent Integraton can be a solution.
Then detailled question is:
Can we have 2 material numbers (e.g. ABC and XYZ) in 2 different R/3 systems refering the same product.
Have the mapping done in MDM (Content Integrator?) to a third material number:123
Replicating the material master 123 to SRM from MDM(?)
Create global Outline Agreements in SRM for Material Master 123.
Distribute the GOA as Outline Agreement to R/3 system 1 with the translation to ABC and to R/3 system 2 with the translation XYZ, all of that during the distribution step (or another).
Have the call-offs quantities correct on 123 in SRM and BW?
IF yes, how is it working, do you have some documentation discribing the scenario and the config steps to do?
Thanks in avance

Hello RD,
That's a good question.
You are on the right way. MDM is the tool for you.
But..
Content Integrator (CI) was first developped for Shell, to address the need of cross-referencing of material/supplier/category IDs, for:
- reporting purpose (actual Spend Analysis)
- mapping purpose (send of XML PO)
CI was later "fusionned" into the new MDM (1.0) solution.
So now, you can not order CI without MDM (even if some SRM slides still present CI).
But mapping API where developped for all inboud/outbound interfaces in SRM, for materials only (good luck for you).
You will find everywhere this piece of code:
Call ECI
    CALL FUNCTION 'BBP_PRODUCT_MAP'
      TABLES
        it_input          = lt_mapping_in
        et_output         = lt_mapping_out
      EXCEPTIONS
        logsys_not_found = 1
        driver_not_found = 2
        product_not_found = 3
        internal_error    = 4
        OTHERS            = 5.
So it is ok, you have the mapping call, but I don't know if all the rest of the process was really "finalized" (call of API mapping in CI, via XI). I personnaly never used it, but I assume it should work.
I my opinion your process is supported by SAP:
- Extract materials from both R/3 and consolidate them as a single product in MDM.
- Distribute this product into SRM.
- Maintain contracts on those products.
- Distribute them to R/3 (The ECI call is also used during contract distribution).
- Call offs corrects in SRM and BW
For MDM documentation, look at netweaver area of service.sap.com.
For MDM/SRM integration, look at SRM 4.0 spend analysis:
https://websmp206.sap-ag.de/~sapdownload/011000358700004424262004E/GlobalSpendOverview.ppt
For SRM contract distribution, call-offs, BW, look at SRM in details in service.sap.com/srm/SRM4.0:
https://websmp206.sap-ag.de/~sapdownload/011000358700001966382004E/contracten.ppt
For SRM5.0, see online help on help.sap.com.
Rgds
Christophe

Two load errors for a standard SRM Contract ODS

We've just installed standard business content for SRM Contract ODS. The standard InfoSource we installed is 0BBP_TD_CONTR_1.   Two loading errors occur:
1st error:
No return value <> 0 allowed in update routines in transfer mode
Diagnosis
The return code was set to <> 0 in routine 'r0063_0SR_TARGVDC ', but the corresponding data field is updated with MOVE. You therefore can not prevent the update of a single data field for certain key values.
System Response
The load process is terminated.
Procedure
When you update with MOVE, you do not have to update all the data records. In this case you should use a start routine in the update rules in which you delete the data records that you do not want to update from    table DATA_PACKAGE. Set the return code for all routines affecting a data field that is updated with MOVE to 0 (also the corresponding key field routines).
Procedure for System Administration
2nd error:
Error converting currency to standard currency (see long text!)     RSBCTBBP
Diagnosis
Record number 1 : Error during currency conversion to standard currency.
The currency JPY of field 0OUTAGTARGT could not be determined.
Procedure
    Possible causes are listed below:
    - Could not find currency tables RSCURTRT or TCURR
    - Could not determine conversion date
    - Could not find an exchange rate for currency JPY in table TCURR
    Check the erroneous data record, currency unit, and date.If all data is
    available, check whether the standard currency was created correctly.
You can change it in transaction <rscur> by changing the settings for InfoObject 0SR_DEFCUR.
Furthermore, the global settings must be transferred from the source system in order to get the currency keys of the currencies (maintained for currency JPY in table TCURR). Use transaction <rsa1> to transfer the global settings. Select 'Source Systems' and choose the entry 'Transfer Global Settings' for the respective source system.
Note: we've transfer the global settings at currency from our SRM source system already, but we still get the same error msgs.
Any idea/solution?
Thanks

Hello All,
As I have already mentioned the condition types in SRM are identically matched to ERP condition type hence the data is flowing correctly and even the idoc has the z-condition type Z123.The IDOC in backend ERP has status 53.
On trial and error method we did unchecked the manual indicator check in the pricing schema for the relevant condition type and because of that now the Z-condiiton type can be seen in the backend ERP contract.
If the indicator was checked, this means that this condition can be maintained only manually (directly in the transaction
ME32K in ECC) and nothing can be transfer from other source.
Note: If the same condition type is being used in more than one pricing procedure then ensure that the check bok is unchecked for agianst the relevant condition type.
Thanks,
Yatin

SRM Contract alert management Workflow - WS10400022 Agents determination

Hi Experts,
I am trying to implement Alert management for SRM Contracts that are expired/ or the threshold is exceeded.
All the necessary configs are done and the event linkage is also done for the workflow Template WS10400022.
The task used in this workflow TS10407926, for agent determination, used the expression &Agents_0001.Agents&
This container value is neither passed from the event linkage binding.
Can anyone explain how this agent determination is done for this workflow?
Your replies are very much appreciated
Cheers,
Prem.

Hello,
OK, i did not see the event linkage between event and workflow...
Currently, &Agents_0001.Agents& is not populated with data coming from the event:
Event is managed by BBP_EV_API_EVENTS_SAVE function modul, and inside this FM by CL_BBP_EVENTS class.
Maybe you should open an OSS message and check all OSS notes dealing with BBP_CONTRACT_CHECK report.
Regards.
Laurent.

New buttons on SRM contract screen? (+)

Hello,
I'm asked to add specific button into the SRM contract screen (BBP_CTR_MAIN transaction). I've been trying to use BBP_CUF_BADI, but achieved none - my customer screen is not displayed at all. However it is called - I've checked it using the debugger. What am I doing wrong?
Thanks in advance.

Hi Cyrill,
Please go through the following lnks,
Add a new button to BID Invitaion
Add customer button to check status screen
Hope it helps.
Thanks,
Pradeep

Authorization object for "add approver" in contracts

Hello, Experts,
I am looking for authorization object for adding approver in contracts.
But without adding authorization for changing contracts.
Regards,
Rami Kleiman - HP

1. you can try to restrict the authorization object ( Manager Role-- /SAPSRM/MANAGER) for contracts to display ( remove the change).
2. you can also change the personalization object key "BBP_WFL_SECURITY" to None ( but i, think this will affect all the objects like shopping carts purchase orders etc..)
Thanks
velu

PI setting for transferring Contract from SRM to ECC - Classic scenario

Dear Experts
SRM 702
ECC 6.0 EHP6
SRM - Classic scenario
Need to understand PI setting for transferring Contract from SRM to ECC, as currently document Central Contract document getting created in SRM, but it is not getting transfer to ECC
No XML message getting triggered in ECC systm as well
can you help me in this
if any additional information needed, pls revert
Regards
Prashant K

Fully approve and release the contract. It will trigger the XML Message.
Go to https://websmp203.sap-ag.de/~form/handler?_APP=00200682500000002672&_EVENT=DISPLAY&_SCENARIO=01100035870000000122&_HIER_… and download the configuration guide & check the PI setting and required Software Components in PI.

SRM contract in awaiting approval state

Hi Gurus,
We are facing an issue where srm contract is approved via a n step badi workflow. But even after completion of workflow the document remains in awaiting approval state.
The step which sets the document status to released status is called in background step in workflow.
If we examine the workflow logs they indicate the successful execution of this release step without any error.
However document is not released.
On further investigation we found that if the business partners who are present in active version and who have got expired at the time of creation of change version causes this to happnen.
Presently we have a workaround by which we replace the expired business partner with a new business partner in active version and then release the change version.
However to develop a permanent fix we are not able to replicate this scenario in our system.
Kindly provide your guidance on this issue.
Regards,
Rohit

Hi Rohit
you have a root cause of this problem
On further investigation we found that if the business partners who are present in active version and who have got expired at the time of creation of change version causes this to happnen.
for testing purpose you can delete this test user or ask basis person to inactivate this user .
1. create a GOA by test user19 buyer1)
2. Approve a GOA by test manager1
3. now delete user1 or inactivate the user1 id BY CHANGING THE VALIDIDTY DATE OF THE USER .
4. revise the GOA by user2 (buyer2) and approve it . will you recreate the same /
RELEASED AT TOP BUT CHANGE VERSION AWAITING FOR APPROVAL IN THE APPROVAL PREVIEW.
if your analysis is true. it is your wonderful investigation.
Muthu

SRM 7.0 'Add Approver' button disabled after rejection

Hi Experts,
I'm working on SRM 7.0(BRF) RFx workflow. I have configured the process level schema and the acceptance by contact person in customizing. When any of the approver rejects the document, it comes back to the creator which is right. But i see the 'Add Approver' button as disabled. But while creating a new document it is showing the 'Add Approver' button, only after rejection, the creator is seeing the button as disabled. Is it the standard behaviour in SRM7.0 ?
Can you guys share your thoughts on this..
Thanks
Ram

Hi,
Please check the note 1378094.
https://service.sap.com/sap/support/notes/1378094
Regards,
Masa

Mass approval functionality for SRM work items

Hi,
We want to implement mass approval functionality for SRM workflow, so that any user is able to approve/reject multiple requests at one go through UWL.
Please guide if it is possible to implement this functinality for task id TS40007952.
Regards,
Avantika

Hi Avantika,
The mass approval functionality can be implemented for simple workflow items which have decisions to complete the work item. (User Decision Type)
In SAP Business Workflow, user can define a task as a decision task by assigning DECISION as the underlying business object type. The task definition allows user to create two or more decision options to complete the task.
The idea is to simply create a custom view/subview for the UWL item and configure it according to your needs.
Have a look at this blog:
Mass/Batch Processing of Work items in UWL
and also check the documentation:
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/4e/72112bc9ea484196f2a5fdc68f5f5f/frameset.htm
Let me know if you have any questions.
Thanks,
Shanti

ERP release for Central Contract Management with SRM 7.0 EhP 1

Hi all,
i would like to have clarification with ERP and SRM release combinations regarding SRM 7.0 EhP1.
Indeed, the "Software Component Matrix for SAP SRM 7.0 EHP1", for Operational Contract Management, tells 'EHP 5 for SAP ERP 6.0 required'.
Moreover, in RKT dealing with SRM EhP1 delta overview, ERP 6.0 with EhP5 is mandatory for an upgrade to SRM7.01.
Nevertheless, i would like to have confirmation regarding this point.
We do not want to use PI to execute the Enterprise Services for CCM. So, we intend to switch BF SRM_WSRM_1 on.
But on the ERP side (EhP5), the only BF dealing with Contract Management is LOG_MM_P2PSE_2 which description is about Service Procurement (and more exactly for item hierarchies).
Does it mean we can use SRM 7.01 with ERP 6.0 EhP4 and without PI but only if we do not use Central Contracts with service hierarchies ?
Thank you for your help.
Regards.
Laurent.

Hi Laurent,
Yes.
When Central contract was designed in SRM 7.0 with ERP EhP4, it was designed with no service hierarchy. But in SRM 7.01 Central contral was enhanced to handle service hierarchy and it works with ERP EhP5. The problem is when we have SRM 7.01 and ERP EhP4. To handle this complication SRM 7.01 was designed to send flat service lines to EhP4 and lower release even though Central contract in SRM has service hierarchy. So while transfering to ERP EhP4 system in standard, all outlines are not consider for transfer and only service lines (Functional items) are transferred to ERP. To do so user needs to maintain the backend destination information of the connected backend system in table BBP_BACKEND_DEST via SM30 transaction with correct system type (for EhP4 system it will be ERP_4.0 and for EhP5 ERP_5.0). SAP Standard program checks this while XML generation for transfer and if system type is ERP_4.0 system it removes all outlines from temp table before generating the XML data. When it is done, ERP has only service lines in its XML and it does the manupulation to create the replication of central contract.
Master Guide (Including Upgrade Information) - SAP SRM 7.01 states:
"The use of SAP NetWeaver PI is optional but it is required for outbound XML-based messaging or for connecting non-SAP planning or execution systems."
So service hierarchy is possible in SRM 7.01 and ECC 6.04 but only with PI. For other CCM functionalities, SRM 7.01 and ECC 6.04 without PI works fine.
Best regards,
Christian Zeuch

'Add Approver' is inactive for SRM contracts

Similar Messages

Maybe you are looking for