Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-LOC-BR (Application Component) Brazil⤷
J1BA (Package) Localization Brazil
IMG Activity
| ID | J_1BNFTYPEREDLFV | Define NF Type Determination for Vendors |
| Transaction Code | S_EB5_05000384 | (empty) |
| Created on | 20090713 | |
| Customizing Attributes | J_1BNFTYPEREDLFV | Define NF Type Determination for Vendors |
| Customizing Activity | J_1BNFTYPEREDLFV | Define NF Type Determination for Vendors |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | J_1BNFTYPEREDLFV |
Use
In this Customizing activity, you assign a nota fiscal type for processing of NF-e to a combination of vendor, plant, and movement type.
Note
If you want to have the same nota fiscal type for processing of NF-e assigned to a specific vendor and movement type, but not to a specific plant, you can leave the field Plant empty, and the system will use the same combination of nota fiscal type, vendor and movement type to all plants.
Requirements
You only maintain this activity if you have a scenario with mixed nota fiscal (NF) types, in which the user needs to decide on the type of NF to be created based on the vendor.
If this is not required, maintain only the activity Define NF Type Redetermination for Goods Movements.
Standard settings
The program access logic works as follows:
- Access the Nota Fiscal type determination for NFe by Vendor (J_1BNFTYPEREDLF) table with the key Plant - Movement Type - Vendor.
- Access the Nota Fiscal type determination for NFe by Vendor (J_1BNFTYPEREDLF) table (when the first access fails) with the key Plant = Space - Movement Type - Vendor.
- Access the Nota Fiscal type determination for NFe (J_1BNFTYPEREDMM) table (when the second access fails) with the key Plant - Movement Type.
- Access the Nota Fiscal type determination for NFe (J_1BNFTYPEREDMM) table (when the third access fails) with the key Plant = Space - Movement Type.
If the system does not find an entry in any of the combinations, then the default NF-type entry from the Movement Type (T156) table is used.
Activities
Example
Note:
An entry for vendor, plant and movement type in this activity overrules any entries made in the Assign Nota Fiscal Category to Sales Document Types and Define NF Type Redetermination for Goods Movement activities.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | I | Valid for countries specified |
| Customizing Attributes | Country Key | Country Name |
|---|---|---|
| J_1BNFTYPEREDLFV | BR | Brazil |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | J_1BNFTYPEREDLFV | 0 | HLB0006310 | General Application Functions |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| J_1BNFTYPEREDLFV | V - View | SM30 |
History
| Last changed by/on | SAP | 20090713 |
| SAP Release Created in | 605 |
