Hierarchy
ECC-DIMP (Software Component) DIMP⤷
IS-AD-SPC-IN (Application Component) Invoicing⤷
AD_SPC_PH3_IN (Package) Development class for Customer Invoicing for SPEC2000
IMG Activity
| ID | ADSPC_S1NVOICE | S1NVOICE OCH and TAX |
| Transaction Code | S_KA5_12001457 | (empty) |
| Created on | 20030226 | |
| Customizing Attributes | S2K_CUST_ACT_ATTR | Attributes for S2K Customizing Activities |
| Customizing Activity | ADSPC_S1NVOICE | BAdI: S1NVOICE OCH and TAX |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | ADSPC_S1NVOICE |
The BAdI ADSPC_S1NVOICE can be used on vendor side to fill the values of the TEIs OCH ('Other Charges-Code and Amount') and VAT ('Value Added Tax-Code and Percent') of the outgoing S1NVOICE message when you want to fill these fields in the message.
The pricing condition types and their values to be considered for OCH and VAT will be passed to the BAdI as character type tables:
- Parameter tables of method CALCULATE_OCH:
Each line of the tables it_header_conditions and it_position_conditions is a character string containing "pricing condition" "space" and "value of the price condition". The values are determined from the E1EDK05 and E1EDP05 segments of the outgoing IDoc.
- Parameter tables of method CALCULATE_VAT:
Each line of the tables it_header_vat and it_position_vat is a character string containing "tax condition" "space" and "value of the tax condition". The values are determined from the E1EDK04 and E1EDP04 segments of the outgoing IDoc.
In your coding you have to :
- Split the data set in the it_header_conditions and it_position_conditions for OCH and it_header_vat and it_position_vat for VAT at the space into the condition and the rate;
- Evaluate the conditions for the outgoing SPEC message;
- Fill the appropriate code along with the rate, again separated by space, into the exporting parameter ET_OCH or ET_VAT, depending on the called method.
Example
As given in the sample code.
Requirements
The pricing condition types to be considered for OCH and VAT have to be made print relevant so that they are printed out in the INVOIC IDoc.
Standard settings
Recommendation
Activities
After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.
If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:
- In the dialog box, enter a name for the implementation of the Add-In and choose Create.
The system displays the initial screen for creating Business Add-In implementations. - On this screen, enter a short description for your implementation in the Implementation Short Text field.
- If you choose the Interface tab, you will notice that the system has populated the Name of the Implementing Class field automatically, by assigning a class name based on the name of your implementation.
- Save your entries and assign the Add-In to a package.
- To edit a method, double-click its name.
- Enter your implementation code between the
method <Interface Name>~<Name of Method>.andendmethod.statements. - Save and activate your code. Navigate back to the Change Implementation screen.
Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not perform the following step: - Choose Activate.
When the application program is executed, the code you created is run through.
Further notes
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| 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 | SAP | 20030303 |
| SAP Release Created in | 471 |
