Do you have any question about this t-code?
Transaction Code: OIAY
Description: Field Selection Order Header Service
Release: S/4HANA and ECC 6
Program:
Screen: 0
Authorization Object:
Development Package: INSC
Package Description: Application Development R/3 Plant Maintenance Customizing
Parent Package: APPL
Module/Component: PM
Description: Plant Maintenance
Overview: The SAP transaction code OIAY is used to manage the field selection order header service. This service allows users to define the order in which fields are displayed in the header of a document. It also allows users to define which fields are mandatory and which are optional. Functionality: The OIAY transaction code enables users to create, change, and delete field selection orders for documents. It also allows users to define the order in which fields are displayed in the header of a document. Additionally, it allows users to define which fields are mandatory and which are optional. Step-by-step How to Use: 1. Enter the transaction code OIAY in the command field. 2. Select the “Create” button to create a new field selection order. 3. Enter a name for the field selection order and select “Save”. 4. Select the “Change” button to edit an existing field selection order. 5. Select the “Delete” button to delete an existing field selection order. 6. Select the “Display” button to view an existing field selection order. 7. Select the “Copy” button to copy an existing field selection order. 8. Select the “Activate” button to activate a field selection order for use in documents. 9. Select the “Deactivate” button to deactivate a field selection order from use in documents. 10. Select the “Exit” button when you have finished making changes or viewing information about a field selection order. Other Recommendations: It is recommended that users familiarize themselves with all of the options available in the OIAY transaction code before making any changes or creating new field selection orders. Additionally, it is important that users test any changes they make before activating them for use in documents, as this will ensure that they work as expected and do not cause any unexpected issues or errors when used in production documents.