SAP ABAP IMG Activity - Index SLASH, page 8
IMG Activity - /
| # | IMG Activity | Transaction Code | Short Description |
|---|---|---|---|
| |
|
||
| 1 | Activate B2B Scenarios for Natural Persons | ||
| 2 | BAdI: Calculation of Total Value | ||
| 3 | BAdI: Calculation of Total Value with RTP Items | ||
| 4 | BAdI: Calculation of Total Value | ||
| 5 | BAdI: Determination of Variant for Delivery Quantity Entry | ||
| 6 | BAdI: Determine Business Process for CT-e | ||
| 7 | BAdI: Step Implementation Before/After DACTE | ||
| 8 | CT-e BAdI: Call Non-SAP System via RFC Communication | ||
| 9 | BAdI: Determination of Custom UI for Logistics Workplace | ||
| 10 | BAdI: Extend B2B Message with an Attachment | ||
| 11 | NF-e BAdI: Store Extension Parameters from ERP Back-End System | ||
| 12 | BAdI: Step Implementation before/after DANFE | ||
| 13 | BAdI: DF-e Status Determination for Gate Monitor | ||
| 14 | BAdI: Determine Business Process | ||
| 15 | BAdI: Simulate/Post Filling of Extension Parameters for Invoice | ||
| 16 | BAdI: Determination of Logical System | ||
| 17 | MDF-e BAdI: Call to Non-SAP System via RFC Communication | ||
| 18 | BAdI: Assignment of Purchase Order Number and Purchase Order Item | ||
| 19 | NF-e BAdI: Call Non-SAP System via RFC Communication | ||
| 20 | NF-e 2.00 BAdI: Extend NF-e with Feeder System Data | ||
| 21 | BAdI: Signature for Outbound Documents | ||
| 22 | BAdI: Validation of Incoming XML Document | ||
| 23 | NF-e: Maintain Batch Parameters | ||
| 24 | Maintain System Security Information | ||
| 25 | Maintain Application-Dependent SSF Information | ||
| 26 | NF-e: Maintain Business Process Determination for Inbound NF-es | ||
| 27 | Maintain Determination of Business Process | ||
| 28 | NF-e: Maintain Assignment of Item Category to CFOP Code | ||
| 29 | Maintain Own Tax Numbers | ||
| 30 | Maintain System Response for Own Tax Numbers | ||
| 31 | Maintain Control Parameters for Process Flow | ||
| 32 | Maintain Control Parameters for Process Flow | ||
| 33 | NF-e 2.00: Define Service Status Request for Authority (SEFAZ) | ||
| 34 | CT-e: Maintain Business Process Determination for Inbound CT-es | ||
| 35 | CT-e: Define Reasons for Rejection | ||
| 36 | CT-e: Maintain Connected Authority Systems | ||
| 37 | MDF-e: Maintain Connected Authority Systems | ||
| 38 | NF-e: Maintain Connected Authority Systems | ||
| 39 | NF-e: Define RFC Destinations for Method Calls | ||
| 40 | NF-e: Name Logical System | ||
| 41 | Maintain Logical System for Own Tax Numbers | ||
| 42 | Determine RFC Destinations for Method Calls | ||
| 43 | Name the Logical System | ||
| 44 | Maintain Mail Sender Parameters for Own Tax Numbers | ||
| 45 | NF-e 2.00: Maintain Version of Message Types | ||
| 46 | NF-e: Define Reasons for Rejection; Assign to Events | ||
| 47 | NF-e: Maintain Receiver Acknowledgment Deadlines | ||
| 48 | NF-e: Maintain Process Determination for Outbound NF-es | ||
| 49 | Define Control Parameters for Process Steps | ||
| 50 | BAdI: Provide LES Documents in ERP | ||
| 51 | Maintain Communication Parameters for Partner Tax Numbers | ||
| 52 | NF-e: Create RFC Destinations | ||
| 53 | Create RFC Connections | ||
| 54 | Define Authority's Status Code | ||
| 55 | CT-e: Define Service Status Request for Authority (SEFAZ) | ||
| 56 | MDF-e: Define Request for Service Status of Authority (SEFAZ) | ||
| 57 | NF-e: Define Service Status Request for Authority (SEFAZ) | ||
| 58 | Define Additions for Log Composition of XML Files | ||
| 59 | CT-e: Maintain Version of Message Types | ||
| 60 | MDF-e: Maintain Version of Message Types | ||
| 61 | NF-e: Maintain Version of Message Types | ||
| 62 | Assign Versions and XML Elements to an Authority Structure for XMLs |