Hierarchy
SLL-NFE (Software Component) xNFE⤷
SLL-NFE-MGM (Application Component) NF-e: Communication Management & Monitoring⤷
/XNFE/CUSB2B (Package) Customizing - Inbound
IMG Activity
| ID | /XNFE/BADI_CUSTOM_UI | BAdI: Determination of Custom UI for Logistics Workplace |
| Transaction Code | /XNFE/83000038 | (empty) |
| Created on | 20140218 | |
| Customizing Attributes | /XNFE/BADI_CUSTOM_UI | BAdI: Determination of Custom UI for Logistics Workplace |
| Customizing Activity | /XNFE/BADI_CUSTOM_UI | BAdI: Determination of Custom UI for Logistics Workplace |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /XNFE/BADI_GET_CUSTOM_UI |
Use
This Business Add-In (BAdI) is used in the SAP Nota Fiscal Eletronica area for the SLL-NFE component.
The user interface (UI) of the process step "Prepare Goods Receipt Posting" is preset in the NFE system. In this Customizing activity, you can implement a BAdI that enables you to replace this preset UI with a custom UI by means of a Web Dynpro component. Your custom Web Dynpro component needs to implement the Web Dynpro interface /XNFE/IF_CUSTOM_UI, which transfers the step-relevant data to your custom UI by means of method STEP_DATA.
Method STEP_DATA transfers the import parameters NF-e header, the corresponding assignment table, and the XML data. The method is called by the NFE Framework every time the custom UI is loaded.
The customer needs to provide the content of the Web Dynpro component and its process flow. Make sure you observe the following:
- The status of the executed step is set solely by the NFE system.
- As in all other manual process steps, the user must change the status of the step using the action "Set Status to 'OK'" or "Set Status to 'Not OK'".
- The NFE system does not check whether all actions or RFC calls of the custom UI are executed.
- The NFE system does not check whether all actions or RFC calls of the custom UI are executed without any errors.
- Error handling and error processing within the custom UI must be made available within your custom Web Dynpro component.
- NF-e data (for example, the NF-e header or the assignment table) must not be changed by the custom UI.
- All actions (such as Post Goods Receipt or Post Invoice) that call a connected system (such as SAP ERP) must not contain any negative effects on the subsequent process steps of the standard process.
Requirements
The BAdI implementation is not activated in the standard system.
The BAdI is not intended for multiple use.
Standard settings
For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18).
Activities
For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.
See also:
The BAdI uses interface /XNFE/IF_BADI_GET_CUSTOM_UI.
For more information, display the interface in the Class Builder.
Example
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | BLICKENSDOER | 20140221 |
| SAP Release Created in | 900 |
