Field status as mandatory while creation of RE-FX Lease Out Contract

Hi SAP Real Estate Friends,
I have a requirement wherein we need to make the field status of some specific fields as mandatory for data input in RE-FX Lease Out Contract. The fields are mentioned below:
1. Profit Centre in Organizational Assignment Term.
2. Payment Terms in Postings Term.
3. Account Determination Value in Postings Term.
4. Resubmission Rule needs to be mandatorily selected by the user creating the RE-FX lease Out Contract.
5. Fixtures and Fittings Characteristics needs to be mandatorily selected by the user creating the RE-FX Rental Object.
Also we need to achieve a requirement that in case a posting has already been carried out for a given RE-FX Contract for a given Account Determination Value, same shall not be available for change in the RE-FX Contract subsequently.
Plz write back with your valuable inputs.
Thanx in advance
Pankaj

Hello,
You can set the field status from this path:
RECACUST > Contract > Dialog > Screen Layout > Field Groups > Field Status per Contract Type
Regards,
Suvarghya.

Similar Messages

BOM Selection Mandatory while creation of Production Order

Hello Friends,
I would like to know that is there any option other than production version which makes it mandatory to have valid BOM must for creation of Production order / coversion of planned order to Production order.
I have tried with Production version option but it doesnt throw any error in case BOM with inactive status has been selected in it & also Production order gets created & released.
Before going for user exit / enhancement option, I just wanted to ensure that it is not possible with standard SAP.
Kindly share your views on the same.
Your urgent replies will be highly appreciated.
Regards,
Tejas

Hello Tejas,
I think this is standard SAP Behaviour.
Try with following exits:
PPCO0018
PPCO0012
Also check out the following link:
[How To Make BOM Mandatory while creating Production Order;
Regards,
Vinod

How to pass smtp_addr(email field) to cremas idoc while creation of vendor?

Hi All,
i am creating the vendors by IDOC by using CREMAS basic type CREMAS05.
There is no email field in any of the idoc segments,as i need to pass the email address being mandatory,
i created the Z segment and added the email field into it and then created the z extension and added this zsegment into the extension.
Now how do i and where do i map this field so that email data is also passed while creating the vendor master.
i have debugged the cremas Function Module IDOC_INPUT_CREDITOR and the data is getting passed segment wise,and for customer segement i.e for the zsegment there is a enhancement section where i need to pass this field,but i do not know how do i map this field and with what structure.
Please let me know how do i handel this/or is there in other way to do it.
Thanks.
RJP.

Hi,
the email is part of the address data. It is therefore not belonging to the customer master data. So it is also not part of the DEBMAS idoctype.
To distribute via ALE accurate customer address data, you need to distribute ADRMAS, ADR2MAS, ADR3MAS idoctypes too.
See [note 384462|https://service.sap.com/sap/support/notes/384462] and [note 306275|https://service.sap.com/sap/support/notes/306275]
BR
Alain

How to make the fields of the table mandatory while creating new entries..?

Hi,
I have created a new Z table which has 6 fields. All the 6 fields are KEY fields and all are of CHAR type. I have generated the table maintenance generator for the same. My requirement is all the fields should be MANDATORY while creating the entries. No field should be BLANK.
When creating the new entries in the table, even if I don't give any values to some of the fields, it is saving the entry. But, it shouldn't happen like that. If any of the field is kept blank, it should not allow the user to save the entry. Can someone tell me how to approach this. Will there be any settings while creating the table which takes care of this.
I read somewhere that this can be done using the Table EVENTS. Can someone tell me what is the code that we should write there in the Events which prevents the user from saving the blank fields. While writing the logic in the events, how to check whether the particular field is BLANK or not. Will the values be stored in any internal table kind of thing..?
My table name is ZCRF_TAB and the fields are FLD!, FLD2, FLD3, FLD4, FLD5 & FLD6. Can someone provide me sample code for my requirement. Thanks in advance.
Best regards,
Paddu.

Hi,I think u have generated Table Maintainance Generator, goto Environment->Modifications->Events
Select appropriate option by using F4,I think value 05 is appropriate for u r requirement.Enter From routine name.Dbl click on the routine.
Write the appropriate code like:
If ZTABLE-FIELD1 is initial.
Message (E000) with "Fill all the manadatory fields".
Thats it.Just look at the following docu with screenshots,by this understand how u can use Table Events:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/abap/how%20to%20implement%20events%20in%20table%20maintenance.doc
Regards,
Rock.

Vendor Master: Field Status madatory donu00B4t work

Hello my friends!!!
I have a problem whit a fields status in vendor master to account group.
I make the field status as mandatory "bank details" to the account group of vendors. This field has several fields within itself.
When I run the t.code MK01, only some fields ask for obligatory and another no. to me. It allows me to happen of screen without completing all the fields.
Why don´t work this check??'
So that it does not work correctly? somebody knows like doing so that it works? Is something this bad one in customizing?
thanks
Regards

If you have made the req entry for the account group and you are using same accoutn group then it should work.
The bank detials is suppressed for MK01 so it will not work
make reqd for MK01 in OMSX tcode

What are the mandatory fields while creation of material master in differen

what are the mandatory fields while creation of material master in different views?

Hi Gopi,
This is purely depends on the function configuration, which would be done MM consultants. Kindly check with them.
thanks & regards
Kishore Kumar Maram

GL Field Status Validation @ PO Creation

Hi Gurus,
We are facing the issue summarized below:-
In FI, itu2019s set up that internal order field as mandatory for GL account 38701404. This is achieved via the field status group at GL account level.
However, with indirect procurement, itu2019s found that no checks taking place at PO creation i.e. when we create a PO and key in the GL account at PO creation, it does not indicate that internal order is a mandatory field for that GL account.
May I know how can the checking triggered during PO creation?
Sample Data used:-
Account Assignment Category: K (Cost Center)
Configuration @ OME9:
CO/PP Order - Hidden Field
Configuration @ OBC4:
CO/PP Order - Mandatory Field
Regards,
Michelle Low

Hi,
You also need to make it manadatory for the Purhcase order creation at Document type level .Please make the accountassigment mandatory ,with internal order ,This will put check during PO creation.
Thanks,
AMIT

Sort Field to be made mandatory while creating maintenance plan(IP42)

Hi Experts,
Please suggest me the way by which i can make the field "Sort field" mandatory while creating maintenance plan (IP42).
Regards,
Vivek

Vivek,
There is no std config to acheive this. Please use IPRM0004 Maintenance plan/item: Customer check for "Save" to accomplish the same.
Mahee

Making task list field mandatory in creation of maintenance plan?

Dear All,
I need your help in configuration of Making task list field mandatory in creation of maintenance plan. I checked with sceen variant config but that also not giving me any option to make the field mandatory.
Is there any note or user exit for it?
Regards,
Kaushal Rai

Dear,
Pls check the exit IPRM0004:Maintenance plan / item: Customer check for time "SAVE".
Regards
Sunil

I am unable to Save the "Note" field while Creation of new Contact

Hi ,
I am unable to save the Note field while Creation of Contact in Web UI.
Its happening in the Dev system but not in the QA Web UI.
I have tried to debug the component BP_CONT, But no use.
Can any one tell me the what could be the problem?
Regards,
DN

Hi DN,
The Notes part comes from the following view:
BP_DATA/Notes (Context Node: NOTES; Attribute: TDLINE)
You can debug in this view.
It could also be a case of missing authorization - the entered text don't get saved when the user does not have authorization to save text in text objects. Please check.
Regards,
Shiromani

How do you know which fields are mandatory while uploading PO using BAPI.

How do you know which fields are mandatory while uploading PO data using BAPI. in a structure how do you know which fields are mandatory.
and also, where how do you check that, the BAPI function module is executed.
Thanks in Advance.
Naveen.

hi
hope it will help you.
Reward if help.
REPORT zpo_bapi_purchord_tej.
DATA DECLARATIONS *
TYPE-POOLS slis.
TYPES: BEGIN OF ty_table,
v_legacy(8),
vendor TYPE bapimepoheader-vendor,
purch_org TYPE bapimepoheader-purch_org,
pur_group TYPE bapimepoheader-pur_group,
material TYPE bapimepoitem-material,
quantity(13),
delivery_date TYPE bapimeposchedule-delivery_date,
net_price(23),
plant TYPE bapimepoitem-plant,
END OF ty_table.
TYPES: BEGIN OF ty_alv,
v_legs(8),
success(10),
v_legf(8),
END OF ty_alv.
TYPES: BEGIN OF ty_alv1,
v_legf1(8),
v_msg(500),
END OF ty_alv1.
*-----Work area declarations.
DATA: x_table TYPE ty_table,
x_header TYPE bapimepoheader,
x_headerx TYPE bapimepoheaderx,
x_item TYPE bapimepoitem,
x_itemx TYPE bapimepoitemx,
x_sched TYPE bapimeposchedule,
x_schedx TYPE bapimeposchedulx,
x_commatable(255),
x_alv TYPE ty_alv,
x_alv1 TYPE ty_alv1,
x_alv2 TYPE ty_alv1.
*-----Internal table declarations.
DATA: it_table TYPE TABLE OF ty_table,
it_commatable LIKE TABLE OF x_commatable,
it_item TYPE TABLE OF bapimepoitem,
it_itemx TYPE TABLE OF bapimepoitemx,
it_sched TYPE TABLE OF bapimeposchedule,
it_schedx TYPE TABLE OF bapimeposchedulx,
it_alv TYPE TABLE OF ty_alv,
it_alv1 TYPE TABLE OF ty_alv1,
it_alv2 TYPE TABLE OF ty_alv1.
DATA: po_number TYPE bapimepoheader-po_number,
x_return TYPE bapiret2,
it_return TYPE TABLE OF bapiret2,
v_file TYPE string,
v_temp(8),
v_succsount TYPE i VALUE 0,
v_failcount TYPE i VALUE 0,
v_total TYPE i.
DATA: v_temp1(5) TYPE n VALUE 0.
DATA: x_event TYPE slis_t_event,
x_fieldcat TYPE slis_t_fieldcat_alv,
x_list_header TYPE slis_t_listheader,
x_event1 LIKE LINE OF x_event,
x_layout1 TYPE slis_layout_alv,
x_variant1 TYPE disvariant,
x_repid2 LIKE sy-repid.
DATA : it_fieldcat TYPE TABLE OF slis_t_fieldcat_alv.
SELECTION-SCREEN *
SELECTION-SCREEN BEGIN OF BLOCK v_b1 WITH FRAME.
*-----To fetch the flat file.
PARAMETERS: p_file TYPE rlgrap-filename.
SELECTION-SCREEN END OF BLOCK v_b1.
AT SELECTION-SCREEN *
AT SELECTION-SCREEN.
IF p_file IS INITIAL.
MESSAGE text-001 TYPE 'E'.
ENDIF.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
*-----To use F4 help to find file path.
CALL FUNCTION 'F4_FILENAME'
EXPORTING
program_name = syst-cprog
dynpro_number = syst-dynnr
IMPORTING
file_name = p_file.
v_file = p_file.
START-OF-SELECTION *
START-OF-SELECTION.
PERFORM gui_upload.
LOOP AT it_table INTO x_table.
PERFORM header_details.
v_temp = x_table-v_legacy.
LOOP AT it_table INTO x_table WHERE v_legacy = v_temp.
PERFORM lineitem.
PERFORM schedule.
ENDLOOP.
DELETE it_table WHERE v_legacy = v_temp.
PERFORM bapicall.
MOVE po_number TO x_alv-success.
APPEND x_alv TO it_alv.
CLEAR x_alv.
*-----To clear the item details in internal table after the operation for a header.
REFRESH: it_item,
it_itemx,
it_sched,
it_schedx.
CLEAR: v_temp1.
ENDLOOP.
v_total = v_succsount + v_failcount.
PERFORM display_alv.
FORM GUI_UPLOAD *
FORM gui_upload .
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
filename = v_file
filetype = 'ASC'
TABLES
data_tab = it_commatable
EXCEPTIONS
file_open_error = 1
file_read_error = 2
no_batch = 3
gui_refuse_filetransfer = 4
invalid_type = 5
no_authority = 6
unknown_error = 7
bad_data_format = 8
header_not_allowed = 9
separator_not_allowed = 10
header_too_long = 11
unknown_dp_error = 12
access_denied = 13
dp_out_of_memory = 14
disk_full = 15
dp_timeout = 16
OTHERS = 17
IF sy-subrc = 0.
*-----To fetch the comma seperated flat file into an internal table.
LOOP AT it_commatable INTO x_commatable.
IF x_commatable IS NOT INITIAL.
SPLIT x_commatable AT ',' INTO
x_table-v_legacy
x_table-vendor
x_table-purch_org
x_table-pur_group
x_table-material
x_table-quantity
x_table-delivery_date
x_table-net_price
x_table-plant.
APPEND x_table TO it_table.
ENDIF.
CLEAR x_table.
ENDLOOP.
ENDIF.
ENDFORM. " gui_upload
FORM HEADER_DETAILS *
FORM header_details .
MOVE 'NB' TO x_header-doc_type.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
input = x_table-vendor
IMPORTING
output = x_table-vendor
MOVE x_table-vendor TO x_header-vendor.
MOVE x_table-purch_org TO x_header-purch_org.
MOVE x_table-pur_group TO x_header-pur_group.
x_headerx-doc_type = 'X'.
x_headerx-vendor = 'X'.
x_headerx-purch_org = 'X'.
x_headerx-pur_group = 'X'.
ENDFORM. " header_details
FORM LINEITEM *
FORM lineitem .
v_temp1 = v_temp1 + 10.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
input = v_temp1
IMPORTING
output = v_temp1.
MOVE v_temp1 TO x_item-po_item.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
input = x_table-material
IMPORTING
output = x_table-material.
MOVE x_table-material TO x_item-material.
MOVE x_table-quantity TO x_item-quantity.
MOVE x_table-net_price TO x_item-net_price.
MOVE x_table-plant TO x_item-plant.
x_itemx-po_item = v_temp1.
x_itemx-material = 'X'.
x_itemx-quantity = 'X'.
x_itemx-net_price = 'X'.
x_itemx-plant = 'X'.
APPEND x_item TO it_item.
APPEND x_itemx TO it_itemx.
CLEAR: x_item, x_itemx.
ENDFORM. " lineitem1
FORM SCHEDULE *
FORM schedule .
MOVE x_table-delivery_date TO x_sched-delivery_date.
MOVE v_temp1 TO x_sched-po_item.
x_schedx-delivery_date = 'X'.
x_schedx-po_item = v_temp1.
APPEND x_sched TO it_sched.
APPEND x_schedx TO it_schedx.
CLEAR: x_sched, x_schedx.
ENDFORM. " schedule
FORM BAPICALL *
FORM bapicall .
CALL FUNCTION 'BAPI_PO_CREATE1'
EXPORTING
poheader = x_header
poheaderx = x_headerx
IMPORTING
exppurchaseorder = po_number
TABLES
return = it_return
poitem = it_item
poitemx = it_itemx
poschedule = it_sched
poschedulex = it_schedx.
IF po_number IS NOT INITIAL.
v_succsount = v_succsount + 1.
MOVE x_table-v_legacy TO x_alv-v_legs.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
ELSE.
v_failcount = v_failcount + 1.
MOVE x_table-v_legacy TO x_alv-v_legf.
MOVE x_table-v_legacy TO x_alv1-v_legf1.
LOOP AT it_return INTO x_return.
IF x_alv1-v_msg IS INITIAL.
MOVE x_return-message TO x_alv1-v_msg.
ELSE.
CONCATENATE x_alv1-v_msg x_return-message INTO x_alv1-v_msg SEPARATED BY space.
ENDIF.
ENDLOOP.
APPEND x_alv1 TO it_alv1.
CLEAR x_alv1.
ENDIF.
ENDFORM. " bapicall
FORM DISPLAY_ALV *
FORM display_alv .
PERFORM x_list_header.
PERFORM build_fieldcat CHANGING x_fieldcat.
x_repid2 = sy-repid.
x_event1-name = 'TOP_OF_PAGE'.
x_event1-form = 'TOP_OF_PAGE'.
APPEND x_event1 TO x_event.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
i_callback_program = x_repid2
is_layout = x_layout1
it_fieldcat = x_fieldcat
i_callback_user_command = 'USER_COMMAND'
i_callback_top_of_page = 'TOP_OF_PAGE'
i_save = 'A'
is_variant = x_variant1
it_events = x_event
TABLES
t_outtab = it_alv
EXCEPTIONS
program_error = 1
OTHERS = 2.
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
ENDFORM. " display_master_data
FORM USER_COMMAND *
FORM user_command USING ucomm LIKE sy-ucomm selfield
TYPE slis_selfield.
READ TABLE it_alv INTO x_alv INDEX selfield-tabindex.
CLEAR : x_alv2,it_alv2[].
LOOP AT it_alv1 INTO x_alv1 WHERE v_legf1 = x_alv-v_legf.
x_alv2 = x_alv1.
APPEND x_alv2 TO it_alv2 .
ENDLOOP.
DATA : it_fieldcat TYPE slis_t_fieldcat_alv.
DATA : x3_fieldcat LIKE LINE OF it_fieldcat.
CLEAR : x3_fieldcat,it_fieldcat[].
CLEAR x3_fieldcat.
x3_fieldcat-col_pos = '1'.
x3_fieldcat-fieldname = 'V_LEGF1'.
x3_fieldcat-reptext_ddic = text-111.
x3_fieldcat-ref_tabname = 'IT_ALV2'.
APPEND x3_fieldcat TO it_fieldcat.
CLEAR x3_fieldcat.
CLEAR x3_fieldcat.
x3_fieldcat-col_pos = '1'.
x3_fieldcat-fieldname = 'V_MSG'.
x3_fieldcat-reptext_ddic = text-112.
x3_fieldcat-ref_tabname = 'IT_ALV2'.
APPEND x3_fieldcat TO it_fieldcat.
CLEAR x3_fieldcat.
x_layout1-colwidth_optimize = 'X'.
x_layout1-zebra = 'X'.
IF it_alv2[] IS NOT INITIAL.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
i_callback_program = x_repid2
is_layout = x_layout1
it_fieldcat = it_fieldcat
i_save = 'A'
i_callback_top_of_page = 'TOP'
is_variant = x_variant1
it_events = x_event
TABLES
t_outtab = it_alv2
EXCEPTIONS
program_error = 1
OTHERS = 2.
ENDIF.
ENDFORM.
FORM USER_COMMAND *
FORM top.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
it_list_commentary = 'Commentry'.
ENDFORM.
FORM BUILD_FIELDCAT *
FORM build_fieldcat CHANGING et_fieldcat TYPE slis_t_fieldcat_alv.
DATA: x1_fieldcat TYPE slis_fieldcat_alv.
CLEAR x1_fieldcat.
x1_fieldcat-col_pos = '1'.
x1_fieldcat-fieldname = 'V_LEGS'.
x1_fieldcat-reptext_ddic = text-108.
x1_fieldcat-ref_tabname = 'IT_ALV'.
APPEND x1_fieldcat TO et_fieldcat.
CLEAR x1_fieldcat.
x1_fieldcat-col_pos = '2'.
x1_fieldcat-fieldname = 'SUCCESS'.
x1_fieldcat-key = 'X'.
x1_fieldcat-reptext_ddic = text-109.
x1_fieldcat-ref_tabname = 'IT_ALV'.
APPEND x1_fieldcat TO et_fieldcat.
CLEAR x1_fieldcat.
x1_fieldcat-col_pos = '3'.
x1_fieldcat-fieldname = 'V_LEGF'.
x1_fieldcat-key = 'X'.
x1_fieldcat-reptext_ddic = text-110.
x1_fieldcat-ref_tabname = 'IT_ALV'.
APPEND x1_fieldcat TO et_fieldcat.
CLEAR x1_fieldcat.
ENDFORM. " build_fieldcat
FORM BUILD_LIST_HEADER *
FORM x_list_header.
DATA: x_list_header1 TYPE slis_listheader.
*-----List Header: type H
CLEAR x_list_header1 .
x_list_header1-typ = 'H'.
x_list_header1-info = text-105.
APPEND x_list_header1 TO x_list_header.
*-----List Key: type S
x_list_header1-typ = 'S'.
x_list_header1-key = text-106.
x_list_header1-info = v_total.
APPEND x_list_header1 TO x_list_header.
*-----List Key: Type S
CLEAR x_list_header1 .
x_list_header1-typ = 'S'.
x_list_header1-key = text-107.
x_list_header1-info = v_succsount.
APPEND x_list_header1 TO x_list_header.
ENDFORM. " build_list_header
FORM TOP_OF_PAGE *
FORM top_of_page.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
it_list_commentary = x_list_header.
ENDFORM. " TOP_OF_PAGE

Credit Check is not working while creation of the delivery

Hi,
Credit check is not performing while creation of the delivery.
As per current settings, there is no credit check at SO level. Ideally, system should show an error message while creation of the delivery if credit limit of the customer is exceeds.
Below is the current OVA8 setting for Delivery group 02.
It was working fine till last week, but due to some unknown changes in customization or master data, same is not working now.
Could you please check below settings and suggest if any setting is wrong?

You talking about the reaction field D am talking about beside to reaction field that is status/Block(check) .
Status/Block(tick) is used to block the document.
Where as you reaction field is used to give the either warning or error message based input you are giving
A and C gives warning message and allow to save the document.
B and D gives error message and will not allow to proceed further
Please check this and try system will block the delivery.
thanks,
Srinu.
Message was edited by: Srinu S

Field Status in Blanket PO

Hi,
I am creating a blanket PO from copying another Blanket PO. But the fields vendor, plant, net price,PO quantity,item category,account assignment category are in display mode. But same is possible in standard PO. I want to create a Blanket PO refferring another one by changing vendor ,net price etc. How can I make those fields in change mode while copying one?There is no problem in creation of Blanket PO.
regards
Ashok

If you use the adopt function, it should be able to copy all the information from an existing PO and in change mode status.
To copy the PO, click "Document Overview On" button, and click the first little button "Selection Variant" to select the old PO, after the PO number display in the space below, HIGHLIGHT the PO (remember not double clicks, if double clicks meaning display), and then click "Adopt" button.
Hope this help you.

Business area and profit centre field to make mandatory in all transactions

Dear Team,
My client wants to make the above mentioned fields mandatory while entering any business transactions. viz. MM,FI / SD transactions. He wants to capture the details Business area wise as well as Profit Centre wise.
Please let me know whether
1. I need to make "Business Area" as well as "Profit Center" field mandatory in "ALL THE FIELD STATUS GROUPS"of particular field status varient. If not which particular field dtatus groups to use. &
2.Whether "Profit Center" or "Cost Center" to make mandatory and to which GL.
Please help.
Waiting for your reply.
Thanks and Regards
Sagar

Hi
A good way to make this Check compulsory in case Document Splitting is active in your system.
Follow the path
IMG>Financial Accounting (New)>General Ledger Accounting (New)>Business Transactions>Document Splitting>Define Document Splitting Chracteristics for General Ledger Accounting.
Here you can make splitting active for Both business Area and profit center.
If any where in the posting system does not find either of Business Area or Profit Center, it would give an error
Thanks & regards
Sanil K Bhandari

Field status variant

HI,
in Tcode OBC5 what is field status variant - use of it
where it is defined & assigned

Hi,
Field status variant is defined in tcode OBC4.
It is the field group which defines which field should be suppressed, mandatory & optional to fill while creating a gl account.
Field group 0001 is the by default from which you can copy for your company purpose & name it as per your requirement. You can also define the new field in the copied field group for your purpose. You can make changes in the copied group by double clicking on them, then it shows the select the group, then double click on anyone you like. It will show the fields from there you can change the setting & highlight the field as per your requirements.
Please let me know if anymore help u need.
Regards,
Prafful Kansal

Field status as mandatory while creation of RE-FX Lease Out Contract

Similar Messages

Maybe you are looking for