Overiding Mandatory Fields for master Agreement Template

Hello,
In the standard creation of the master agreement template the CONTACT field is mandatory. To me, this does not make sense because a template would need to be created for every contact/supplier. We want to make the CONTACT field optional for master agreement templates. I am trying to create a page customization with the following properties to accomplish this:
UI ID:contracts.contract.ui.buyside.default
Name:Master AgreementParent
Class: Master Agreement
Field ID: Contact
Property: required
Value: no
Dimension on parent set
Dimension Field : IS_TEMPLATE
Dimension Field Type: Boolean
Dimension Value: yes
I can not seem to make it work. Any suggestions? Is this even possible?
Thanks in advance,
Kyle

Thanks for the quick reply. I was hoping to avoid a dummy vendor. This is sure a strange piece of software.
Kyle

Similar Messages

Mandatory Field for Master Data Creation

Dear Experts,
How can I make "Street 2" Field as a Mandatory Field when I create Customer Master data (XD01) ?
Thanks in advance for your kind support.
Best Regards.
Ripon

Hi
KIndly go to the belwo path and choose Create customer centrally and make the street field mandatory
SPROFinancial accounting-Accounts receivable and accounts payable -Customer accounts-Mastr data---Define screen layout per activity (customers)
By doing above system will show mandatory for all account group when creating customer master thjrough XD01
If you want to do mandatory for account groupo the n go to t code OBD2
Regards
Damu

Mandatory fields for vendor master load

Hi Experts,
what are the mandatory fields for the vendor master upload? how can I find that?
Thanks for the help.

In addition, you can also refer the links:
http://www.auditnet.org/docs/SAPR3AccountsPayable.txt
http://users.ev1.net/~gmorris/securitydocs/SAPR3AccountsPayableMatrix.doc
Hope thisll give you idea!!
<b>P.S award the points.!!! !!!</b>
Good luck
Thanks
Saquib Khan
"Some are wise and some are otherwise"

Requirements for master data template

HI,
Please let me know the basic requirements for master data template. What all the infotype to be involved in collecting master data template.
Thanks and regards,
Aylwin

Hi Alwyn,
If you dealing with india payroll definately Yes subject to you business process again.
Even though it is indian payroll some item may not applicable
For exmple other income resourece will be if you go to manufaturing industries you may face problem even though they got some they don't want reveal it to the employee.
in such that infotype is not required as per your business process.
Some states like UP there is no profession tax. Genrally we say profession tax need to be configure you need that master data.
If such case that might be wrong for that you need to give all the info
use PA30 t code go in side check what are the mandatory fields and take them as master data fields and put it in template.
If your client is able to give other field you can very well add them no harm in it.
But make sure you filled mandatory fields
That is the reason i was asking you to tell which coutry payroll you using
Best Regards

Mandatory fields for xd01

hai,
what are the mandatory fields to create the datas for xd01.(customer master data).
regards
surender

HI
MANDATORY FIELDS FOR CREATING CUSTOMER DATA ARE:
Account Group---ktokd(field name)
Name---Name1
Search term----sortl
postal code----pstlz
country-----land1.
Regards,
vineela

Source list mandatory only for scheduling Agreement

Hi Gurus,
My client wants to make source list mandatory only for scheduling agreement. While creating scheduling agreement for a particular type and saving it should be mandatory. But for Purchase orders and contracts this is not required. If i do it through OME5 then it becomes mandatory for PO and SA both. Also if i set in material master it becomes mandatory for both.
Please let me know if there is way to do it.
Thanks and Regards,
Yuvaraj

It doesn't make too much sense, but... do you want to be sure (garantee) that the source list has been created and it is relevant to MRP when you have a schedule agreement? perhaps you can use a user exit when you save the schedule agreement to create the source list.
There is no standard functinality that's allow you to requirer the source list according the po type.
regards.

Workflow for Master Agreement (Publish to ERP)

What is the best practice for approval workflow before publishing a master agreement from eSource to ECC?
In the interest in keeping the source-of-truth within a single application we do not want to keep approval workflow of Outline Agreements in ECC as it is currently when moving the creation of the master agreement functionality to eSource. There is no inherent workflow functionality for master agreements in eSource. Are there customizations and/or best practices for having workflow of master agreements such that the Publish to ERP would not be possible until approval has been done within the eSource application?

Hi,
As you rightly said, Work flow support is not available in MA and more specifically before sending it to ERP
Here are some options you may want to consider:
- Try to use ACL/Security rights to control who can publish to ERP. For instance only the "document owner" can publish and the document owners are responsible. You can put a message or ask the publisher to enter some values on extension fields on who all approved this document.
- Try using approval functionality in ERP if that works. that may be the simplest..
The following options require heavy customization & scripting:
Leverage workflow support from other docs
- Tie an User defined business document (UDO that supports workflow) with MA. Provide a custom action, which will create a UDO biz doc instance and trigger a workflow behind the scenes. MA will have a reference to UDO and vice versa. Users will approve the UDO. In your Pre Publish to ERP script check for the approval conditions of UDO and work with that.
- if MA is created from Projects try using project workflow for the business process..
Good luck!
Thanks, Baski

Mandatory fields for BAPI_ACC_DOCUMENT_POST

Hi
I am getting the follwing data from the file (Which is coming from oracle) invoice number and the amount,
from that i have to use Fb70 tcode for posting ,Please help me what are the mandatory fields for FB70,
how will get those fields from SAP. How to use the BAPI ?
Regards
Pabs

hi
check out this thread
Re: BAPI_ACC_DOCUMENT_POST
hope this helps
regards
Aakash Banga

Mandatory Fields for IDOC ORDERS01 for Pricing Condition EDI1 to trigger

Hi ,
I'm Testing an Inbound ORDRSP using we 19 for Pricing Conditions EDI1. What are the Mandatory Fields for IDOC ORDERS01
Thanks

hello,
I think it's better to execute VA01 to create a sales order; in that way you should have an idea of mandatory fields.
Thanks.

Can any one pls tell me the mandatory fields for BAPI_ACC_DOCUMENT_POST

hi all ,
Can any one pls tell me the mandatory fields for BAPI_ACC_DOCUMENT_POST
what all data i need to give to post a document.
Thanks and Regards
JK

Hi...
part of my source code:
** Header Data " Sending comp code
wa_documentheader-comp_code = 'XXXXX'.
wa_documentheader-doc_date = '20060620'.
wa_documentheader-pstng_date = '20060620'.
wa_documentheader-doc_type = 'XX'.
wa_documentheader-username = sy-uname.
wa_documentheader-ref_doc_no = 'XXxxxxxx'.
wa_documentheader-header_txt = 'Text Header.
wa_documentheader-bus_act = 'XXXX'.
*it_currencyamount
wa_currencyamount-itemno_acc = '1'.
wa_currencyamount-currency = 'COP'.
wa_currencyamount-amt_doccur = 1943.
APPEND wa_currencyamount TO it_currencyamount.
*it_accountpayable
wa_accountpayable-itemno_acc = '1'.
wa_accountpayable-gl_account = '1234567890'.
wa_accountpayable-bus_area = 'DIV'.
wa_accountpayable-item_text = 'Text 1 XXxxxxx '.
wa_accountpayable-pmnt_block = ''.
APPEND wa_accountpayable TO it_accountpayable.
*it_accountgl
wa_accountgl-itemno_acc = '2'.
wa_accountgl-gl_account = '1234567890'.
wa_accountgl-item_text = 'Text 2 XXxxxxx'.
wa_accountgl-bus_area = 'DIV'.
APPEND wa_accountgl TO it_accountgl.
wa_currencyamount-itemno_acc = '2'.
wa_currencyamount-currency = 'COP'.
wa_currencyamount-amt_doccur = ( 1943 ) * -1.
APPEND wa_currencyamount TO it_currencyamount.
CALL FUNCTION 'BAPI_ACC_DOCUMENT_CHECK'
EXPORTING
    documentheader = wa_documentheader
TABLES
    accountgl      = it_accountgl
    accountpayable = it_accountpayable
    currencyamount = it_currencyamount
    return         = it_return.
clear it_return.
CALL FUNCTION 'BAPI_ACC_DOCUMENT_POST'
      EXPORTING
        documentheader = wa_documentheader
      TABLES
        return         = it_return
        currencyamount = it_currencyamount "currencyamount
        accountpayable = it_accountpayable "accountpayable
        accountgl      = it_accountgl "accountgl
      EXCEPTIONS
        OTHERS         = 01.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.

Mandatory fields for mapping in ORDERS idoc.

Hi
I m working on File to idoc scenario for creation of sales order in ECC 6.0 , now I want to know what are the mandatory fields in ORDERS idoc which needs to be populated or else disbaled so that the sales order gets created properly in the ECC 6.0..
Pl let me know the method of finding mandatory field for mapping for any idoc and which fileds of idoc are to be disabled.
Pl help ..
ans will be rewarded .
thanks & rgds
mojib

HI,
U can disable the control record segment and in the IDOC adapter use the option apply control record from payload.
If you have set the Apply Control Record Values from Payload indicator in the receiver IDoc adapter, the following fields are filled from the IDoc-XML payload:
·        MESCOD
·        MESCFT
·        TEST
·        EXPRSS
·        STD
·        STDVRS
·        STDMES
·        SNDSAD
·        SNDLAD
·        RCVSAD
·        RCVLAD
·        REFINT
·        REFGRP
·        REFMES
·        STATUS
·        DIRECT
·        OUTMOD
·        CREDAT
·        CRETIM
read the information in below link:
http://help.sap.com/saphelp_nw70/helpdata/EN/ab/bdb13b00ae793be10000000a11402f/frameset.htm
thnx,
chirag

PS: Setting Project Profile as a mandatory field for Project Definition

Hi,
I would like to know how to set Project Profile as a mandatory field for Project Definition (CJ20N or CJ01). I tried to look for controls at OPUK config but the Project Profile is not available for definition - either mandatory, optional, suppressed, etc. Would appreciate if you can share your expertise on this.
Thanks!
Regards,
Vivian

Hi,
I would like to know how to include some additonal fields in OPUK/OPUJ. We have defined some .INCLUDE component / fields to SAP standard table PRPS/PROJ. We want those fields to also appear in OPUK/OPUJ so that we could also defined their characteristics - whether input, mandatory, suppressed, etc.
Thanks!
Regards,
Vivian

Mandatory Field for Entering Delayed Reason for project during scheduling .

Hi Friends
Here I have a question on "Scheduling"?
My Client want an mandatory field for entering the delay reason if any phase or tasks or project definition get delayed.
Your input would be highly appreciated
Regards,
YAGHAG

Hi Abhijit,
Thanks for your prompt reply.
I am implementing cprojects 4.5 in PLM 7.0 and not in PPM 5.0.
Regards

Mandatory field for TIN No, or Contact Person

HI Expert,
Can anyone please tell me code for Mandatory field for TIN number or Contact person at the time of adding Purchase Order.its possible by SP i tried for it but its variable so pls anyone have any idea.
Sudhir

Hi Sudhir,
Try This.
FOR Contact Person-----
IF EXISTS (SELECT DocEntry FROM [dbo].[OPOR]
WHERE
((CntctCode IS NULL OR CntctCode = '')
AND DocEntry = @list_of_cols_val_tab_del))
BEGIN
SELECT @error =1, @error_message = 'Your Error Msg1'
END
END
For TIN No.-------
IF (@object_type = '22' AND @transaction_type= 'A')
BEGIN
IF EXISTS (SELECT DocEntry FROM [dbo].[POR12]
WHERE
((TaxID11 IS NULL OR TaxID11 = '')
AND DocEntry = @list_of_cols_val_tab_del))
BEGIN
SELECT @error =1, @error_message = 'Your Error Msg 2'
END
END
Regards
Ashutosh T

Mandatory fields for VF01, ME51, XD01, Co40

can anyone tell me the mandatory fields for the tcodes to do BDC:
VF01
ME1
XD01
CO40

Hi,
ME51,VF01 -- No mandatory fields for these transactions.
XD01-- account group and customer number are mandatory.
CO40- Planned order mandatory.
Regards,
Jagadish.

Overiding Mandatory Fields for master Agreement Template

Similar Messages

Maybe you are looking for