General Billing Interface

hi,
Pls let me know in detail @ this functionality with scenario. Also can we create billing without any Sale order or delivery in SAP, masters in SAP?
Wht all things will be required to be maintained in sap?
Regards,
Laxmikant

Dear Laxmikant,
Go thorugh this SAP help link it will help you about Billing functionality and process in the SAP.
http://help.sap.com/saphelp_47x200/helpdata/en/dd/560e5d545a11d1a7020000e829fd11/frameset.htm
I hope this will help you,
Regards,
Murali.

Similar Messages

AM010 with general billing interface and CPD customer

Hi all
I'm trying to create a SD invoices with the general billing interfaces. All the partner are One-time customers. In simulation launch no error is generates, but when i search to create the final posting, the AM010 "address doesn't exist" create a abend message. What can generate this error?
ciao
Davide

Using general billing the program take the address data from the input structure; the problem happen in my case because in my custom idoc input process, using the same invoice list number, i make before a simulation launch with the function GN_invoice_create, and after the registration launch with the same function. SAP thinks to have memorized the new address in the simulation phase, but in reality he don't has committed the data. When enter in registration phase he try to search the "temp" address in DB linked to simulated document, obvisiously don't finding it and generating the error. I must clear the field address number in the VBPA parameter of GN_invoice_create before launch the registration phase.
With this solution SAP create the SD invoice but lost the address linked to the document, usign the CPD customer description.

General user interface items

This question was posted in response to the following article: http://help.adobe.com/en_US/aftereffects/cs/using/WSB8DDC87E-577E-4099-A5D0-B266E9543E09a. html

How do I turn of all anti-aliasing on the After Effects User Interface within Mac OSX? I've got LCD Font Smoothing turned off in the System Preferences > General, and increased the minimum size of smoothing to above 12 points, and think that the interface fonts are surely smaller than 12 points, but they're still being anti-aliased.
For me, and I might be alone in this, I really like clear, pixel edged fonts, and this is especially true on the new Retina Macbook Pro when running in native 2800x1800 mode.

General Ledger Interface Table

Does anybody know which field on the GL Interface Table will hold the description for a journal line?

REFERENCE4 (Journal entry name): Enter a journal entry name
for your journal entry. Journal Import creates a default journal
entry name using the following format: (Category Name)
(Currency) (Currency Conversion Type, if applicable) (Currency
Conversion Rate, if applicable) (Currency Conversion Date, if
applicable) (Encumbrance Type ID, if applicable) (Budget Version
ID, if applicable). If you enter a journal entry name, Journal Import
prepends the first 25 characters of your journal entry name to the
above format.
REFERENCE5 (Journal entry description): Enter a description for
your journal entry. If you do not enter a journal entry description,
Journal Import automatically gives your journal entry a description
using the format: Journal Import Concurrent Request ID.

General Ledger Interface i got a an answer ...

Hi friends,
this program is working fine now check it ...
CREATE OR REPLACE PACKAGE BODY APPS.gl_interface_pkg
AS
PROCEDURE gl_interface_proc (errbuf OUT VARCHAR2, retcode OUT VARCHAR2)
IS
-- cursor declaration
CURSOR gl_cur
IS
SELECT *
FROM xtg_gl_interface_stg;
TYPE gl_data_tbl IS TABLE OF xtg_gl_interface_stg%ROWTYPE
INDEX BY BINARY_INTEGER;
rec_cur gl_data_tbl;
l_currencycode VARCHAR2 (25);
l_set_of_books_id NUMBER (5);
l_flag VARCHAR2 (2);
l_error_msg VARCHAR2 (100);
l_err_flag VARCHAR2 (10);
l_category VARCHAR2 (100);
l_userid NUMBER (10);
l_count NUMBER (9) DEFAULT 0;
BEGIN
DELETE FROM gl_interface;
COMMIT;
OPEN gl_cur;
FETCH gl_cur
BULK COLLECT INTO rec_cur;
CLOSE gl_cur;
FOR rec_cur IN gl_cur
LOOP
l_count := l_count + 1;
l_flag := 'A';
--Category Column Validation
BEGIN
SELECT user_je_category_name
INTO l_category
FROM gl_je_categories
WHERE user_je_category_name = rec_cur.user_je_category_name;
EXCEPTION
WHEN OTHERS
THEN
l_flag := 'E';
l_error_msg := 'Category does not exist ';
fnd_file.put_line
(fnd_file.LOG,
'Inserting data into the Interface TABLE'
|| '-'
|| l_count
|| ' '
|| l_error_msg
END;
--End Category Column Validation
--User ID column validation
BEGIN
SELECT user_id
INTO l_userid
FROM fnd_user
WHERE user_id = rec_cur.created_by;
EXCEPTION
WHEN OTHERS
THEN
l_flag := 'E';
l_error_msg := 'User ID does not exist ';
fnd_file.put_line
(fnd_file.LOG,
'Inserting data into the Interface TABLE'
|| '-'
|| l_count
|| ' '
|| l_error_msg
END;
--End of Created_by OR UserID column Validation
--Set of books Validation
BEGIN
SELECT set_of_books_id
INTO l_set_of_books_id
FROM gl_sets_of_books
WHERE set_of_books_id = rec_cur.set_of_books_id;
EXCEPTION
WHEN OTHERS
THEN
l_flag := 'E';
l_error_msg := 'set of Books ID does not exist ';
fnd_file.put_line
(fnd_file.LOG,
'Inserting data into the Interface TABLE'
|| '-'
|| l_count
|| ' '
|| l_error_msg
END;
--Cuurency Code Validation
BEGIN
SELECT currency_code
INTO l_currencycode
FROM fnd_currencies
WHERE currency_code = rec_cur.currency_code
AND currency_code = 'USD';
EXCEPTION
WHEN OTHERS
THEN
l_flag := 'E';
l_error_msg := 'currency code does not exists';
fnd_file.put_line
(fnd_file.LOG,
'Inserting data into the Interface TABLE'
|| '-'
|| l_count
|| ' '
|| l_error_msg
END;
IF l_flag != 'E'
THEN
fnd_file.put_line (fnd_file.LOG,
'Inserting data into the Interface TABLE'
INSERT INTO gl_interface
(status, set_of_books_id,
accounting_date, currency_code,
date_created, created_by,
actual_flag, user_je_category_name,
user_je_source_name,
user_currency_conversion_type,
segment1, segment2,
segment3, segment4,
segment5, entered_dr,
entered_cr, accounted_dr,
accounted_cr, GROUP_ID,
reference1, reference2,
reference4, reference5
VALUES (rec_cur.status, rec_cur.set_of_books_id,
rec_cur.accounting_date, rec_cur.currency_code,
rec_cur.date_created, rec_cur.created_by,
rec_cur.actual_flag, rec_cur.user_je_category_name,
rec_cur.user_je_source_name,
rec_cur.user_currency_conversion_type,
rec_cur.segment1, rec_cur.segment2,
rec_cur.segment3, rec_cur.segment4,
rec_cur.segment5, rec_cur.entered_dr,
rec_cur.entered_cr, rec_cur.accounted_dr,
rec_cur.accounted_cr, rec_cur.GROUP_ID,
rec_cur.reference1, rec_cur.reference2,
rec_cur.reference4, rec_cur.reference5
END IF;
l_flag := NULL;
l_error_msg := NULL;
END LOOP;
COMMIT;
END;
END;
Edited by: sandeep on Jul 14, 2011 9:54 AM
Edited by: sandeep on Jul 14, 2011 6:15 PM
Edited by: sandeep on Jul 14, 2011 6:17 PM

Hello,
I think the way you define your variables are not correct..
Try doing this for all your variables:
TYPE status_TBL IS TABLE OF gl_interface.status%TYPE INDEX BY PLS_INTEGER;
TYPE set_of_books_id_TBL IS TABLE OF gl_interface.set_of_books_id%TYPE INDEX BY PLS_INTEGER;
+...+
+...+
TYPE reference5_TBL IS TABLE OF gl_interface.reference5%TYPE INDEX BY PLS_INTEGER;
v_status status_TBL;
v_set_of_books_id set_of_books_id_TBL;
+...+
+...+
v_reference5 reference5_TBL;
Hope this help,
Vikram

General User Interface Data Flow Problem (LabVIEW 2012)

I am having problems reading & checking user input to a tabbed panel (see the tab "Test Parameters" in the attached example).
In essence I need to set and test many parameters.
In the example I need to create a binary mask from four select switches. On its own the scheme works a treat but in the context of
the tabbed panel the switches are never "reached". I tried to put a while structure around the switches (which works ex-vivo,
see attached "channelselect.vi") but the switches are never reached when I step through the code. Basically, I do not want to
leave the pane until all parameters have been set and verifyied.
I tried case structures (by group), flat structures (group by frame), Event Structures (event by nutton change)
I anticipate the same problems with the other sets of parameters. I need to change - set - check, in any order.
Understand the "setting" mechanism is tied to a sub-vi/class method where the parameter is tested, set and verified.
This is a long winded approach to ask the basic question "how would you lay it out"? I am sure this is a basic misunderstanding
on my part of the dataflow paradigm. I am not looking for anyone to do my work for me but I am looking to understand how this
works so I can get on with my day.
Thanks in advance for any help you can proffer.
Solved!
Go to Solution.
Attachments:
playUI.vi ‏96 KB
channelSelect.vi ‏12 KB

You can still have the tab control. You just don't need to do all of your processing when the user changes the tab. You can make event cases on the button presses as well. Treat the VI as an entire VI, not individual tabs that you have to manage.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
Attachments:
playUI.vi ‏82 KB

External billing

I have a scenario where sales orders are entered in an external system and every night uploaded to SAP to perform pricing and create billing document. General billing interface is used to load billing information into SD interface for forwarding to Accounting. You only create billing documents, so no sales orders or deliveries created in SAP as this being services offered.
Points will be rewared
Thanks,
Peter

Hi Peter,
I could not get understand your question properly... Are you saying that you need to know some way to upload the orders into SAP rather than using the billing interface to post the billing directly to SAP from external system.
Kindly explain the situation...

External billing with NO_MARA

Billing is being created in an external system. We need to load billing data to SAP, create invoices, track AR, and collect CASH. We need to do the Billing to Cash part of the Order to Cash process in SAP. We found the BAPI used in the General Billing interface. We need to load the prices from external and we want to not maintain any sales materials in the SAP system. We are using BAPI_BILLINGDOC_CREATEMULTIPLE with the NO_MARA selected. We use CONDITIONDATAIN to transfer the item price. We can create a document but the price is always 0.00. I suspect CONDITIONDATAIN should use something other than PR00 since we are entering the material and price from external.

This link indicates it might be the billing relevance of the item category. Re: BAPI_BILLINGDOC_CREATEMULTIPLE Billing Doc not created
Was using item category TAN which has FKREL set to A (Delivery-related Billing Document). Is there a specific item category that should be used in VTFF (Copying Control for Billing Documents) for the FX doc when trying to load data with the NO_MARA option?

GN_INVOICE_CREATE - Creates Invoice but not visible (for Report RVAFSS00 )

Hi,
I am running GN_INVOICE_CREATE using SE37. I have supplied the data and stepped through the code. At the end of the execution - I get a successful message stating that the "Document 9000007 is saved". If I go into VF03 and try to bring up Billing document 9000007 - I get the error message "Billing document 9000007 does not exist."
I am not sure if i am supplying all of the input parameters correctly to make sure that the transaction is committed. I cannot find enough documentation about GN_INVOICE_CREATE parameters. The only information I did find for the input is under the Billing (SD-BIL)->Billing->The General Billing Interface->Function Module Parameter at http://help.sap.com/saphelp_46c/helpdata/en/dd/5615db545a11d1a7020000e829fd11/content.htm and http://help.sap.com/saphelp_46c/helpdata/en/dd/5615b4545a11d1a7020000e829fd11/content.htm . But that does not describes all of the input parameters like (VBSK_I, WITH_POSTING, CALLER_TYPE, I_WITHOUT_REFRESH, ID_NO_ENQUEUE, ID_KVORG, ID_NO_DIALOG, ID_NEW_CANCELLATION)
Do I need to create a wrapper RFC and call a BAPI_COMMIT_WORK as in BAPI_SALESORDER_CREATEFROMDAT2? Or am i passing the parameters incorrectly:
Here is what I am passing in SE 37:
DELIVERY_DATE =                   08/14/2006
INVOICE_DATE =                     08/14/2006
INVOICE_TYPE =                     FX
PRICING_DATE
VBSK_I
WITH_POSTING =                     A
CALLER_TYPE
I_WITHOUT_REFRESH =                X
ID_NO_ENQUEUE
ID_KVORG =                         06
ID_NO_DIALOG =                     X
ID_NEW_CANCELLATION
The XKOMFKGN and XKOMFKKO tables I believe are correct based on the Communication Structure help files.
Any help in figuring this out is appreciated. Also, if you can let me know what the following field inputs are -VBSK_I, WITH_POSTING, CALLER_TYPE, I_WITHOUT_REFRESH, ID_NO_ENQUEUE, ID_KVORG, ID_NO_DIALOG, ID_NEW_CANCELLATION.
The reason I am going through this RFC is that we are looking at using Report RVAFSS00 to import a file that then runs the GN_INVOICE_CREATE to create billing documents with external transactions as defined in the General Billing interface.
Regards,
Jay

Did not find the documentation for the fm any where, i think best place to look for is OSS.
Parameter: ID_NO_DIALOG is for suppressing some shipping related screen and ID_NO_ENQUEUE is for locking sales order or delivery doc.
By using where used list of the function module, some times it's possible to find out the use of other parameters.
Hope this helps.
Regards
Sridhar

Purchase Rebate - Error during Settlement - MEB4

Hi Experts,
For the Purchase Rebate Scenario, I have followed the following steps :
1. Create Rebate Arrangement
2. Create PO
3. Goods Receipt
4. Invoice verification using MIRO
5. Check Update of business volume T-code : MEB6 Update of business volume was successful.
6. Execute Interim Setttement - Tcode MEB4
In this step, I am getting this error "Error messages generated during billing document check run" Message no. MN236
Settlement accounting for rebate arrangement 45 is carried out using the general billing interface in the system (credit-side settlement type) or the general billing interface for customer billing documents (debit-side settlement type).
It is also possible that credit memos (invoice verification, credit- side settlement type) are involved.
The documents cannot be created without errors.
Please help me out in this. What could have possibly gone wrong?
Thanks,
Maniraj

GO to SPRO-MM-Purchasing-Subsequent (End-of-Period Rebate) Settlement-Control of the "Subsequent Settlement" Process - Vendor Billing Document: Document Types
Select the following billing type
BM10     Fin.Set.Rebate,Plant
BM11     Fin.Set.Rebate, POrg
BM30     Part.Set.Rebate,Plnt
BM31     Part.Set.Rebate,POrg
double click on it and at the ente of the screen you will see control 2
here you need to enter the tax code

Issue in Vendor Rebate Settlement (ECC 6.0)

Hello All,
We recently upgraded from SAP 4.7 to ECC 6.0. In the new system, the vendor rebate settlement (MEB4) is giving the following errors:
1. Error messages generated during billing document check run
Message no. MN236
Diagnosis
Settlement accounting for rebate arrangement 85 is carried out using the general billing interface in the system (credit-side settlement type) or the general billing interface for customer billing documents (debit-side settlement type).
It is also possible that credit memos (invoice verification, credit- side settlement type) are involved.
The documents cannot be created without errors.
2. For vendor 1885 no partner exists for partner function PI
Message no. WS723
The process used to work in the 4.7 version and no changes have been made to the configuration in the new system. Can someone please suggest the reason for these errors and how they can be resolved?
Thanks,
Rugmani

HI,
Please chk in the config....
SPRO>MM->Partner Deter->Partner setting in Rebate Arrangement->Define partner schemas for Rebate..
Here please check the partner function "PI" is made mandatory...
You can main the Partner function "PI" in the agreement itself...
Goto-- txn.MEB2-- enter the agreement no... inside click the icon "Agreement Partner" or (Ctrl+F2) and maintain the partner function PI..
Regards
GK.

IDOC SD INVOICES

Hi all
First post here.
My society needs to implement a not-very-standard flow:
we have a third party society (with SAP R/3 release 4.7) which make us the logistical process ( SD orders->delivery->invoices ) and the financial module; from the 2008 all the financial module (with CO) has to be passed to our SAP R/3 (4.6C). Our intention is to use IDOC for generate data in our system.
The points are:
1 - For time, managemant and money problems we dont copy SD orders and delivery; our intention is to transfer with idoc MM movements for alignment between the stocks and SD invoices (these, after,will generate the FI documents for the financial necessities). We copy SD invoice and not directly FI/CO documents for statistical reasons.
2 - My problem is with the invoices; i know SAP permit to bill external documents without delivery or SD order using to general billing interface and that this process use the function module GN_INVOICE_CREATE. My intention is to use the type message INVOIC with the process SBII (i make a Z. of this process with Z. function removing all the blocking controls on the deliveries) which also use the GN_INVOICE_CREATE. Shortly the partner send me his invoice with INVOIC02 format like a customer, but i register the INVOIC not as a MM invoices but i create a SD copy how external billing.
3 - We prefer use external numeration for the SD invoices, so to take our partner numeration (perfect alignment between the systems, possibility to register in error case with the same number in the past).
The questions are: the point 2 is practicable with IDOC? The point 3 (external numeration) also?
Thanks
Davide

Hello Jelena,
Totally agree with you,
please let me share the actual process :
- sales orders are created in an external system that will send them to SAP (via Idoc).
- sales order are invoiced in SAP,
--> if there is a modification that occurs on external system on the sales order , the SAP SD invoice should then be canceled, SD order updated and then re-invoiced.
This is the behavior requested for the moment
If you have any advices Thank you in advance

Order-related intercompany

Dear All,
Can some one provide some details regarding the Order-related intercompany billing?
Regards
Sandeep

Hi Sandeep,
The standard system only generates an intercompany billing document for the cross-company code sales if a delivery is involved.
     The order-related intercompany billing (e.g. credit and debit memo) and the cross company process for service items, leasing and maintenance items and third-party items is only possible with a kind of workaround.
     There, the creation of the internal billing document is executed with report RVIVAUFT via the specification of an invoice document (billing document or credit memo).
Two options must be distinguished:
   a) directly that is, explicit specification of the invoice documents (TA se38)
b) indirectly that is, report RVIVAUFT is called via output control with selection program RSNAST00 and output type RDIV.
The report RVIVAUFT uses the function module GN_INVOICE_CREATE that is also used for the general billing interface to generate billing documents with external data.
      Via note 381042 (SAPKH46C15) report RVIVAUFT has been delivered with many corrections up to this HP level.
Since then the following applies:
     Report RVIVAUFT instead of report ZZIVAUFT
     Standard requirement 036 'Item/order related IB' instead of Copying requirement 613
     Standard requirement 018 'Order-related IB' instead of customer-specific output requirement 990.
     Standard ouptput type RDIV instead of customer-specific output type ZZIV.
The 63459 and 381042 are important notes regarding this process.
I hope this information will help you.
Regards
Roop

Brief about enhancements and user exits

hai,
can any one tell me what are enhancements and user exits in sap sd,
their signifcance & configuration
regards
sriram

hi,
an example of user exit
In case of Inbound DELINS IDOC (830 type) once there was a requirement of taking the Target *** Qty required and the Target *** Date for a specific customer who was not sending *** Qty Received by him.
So for that specific customer we used the search term and added the same in the Data 4 field of the IDOC under segment E1EDK09.
There was one user exit available in IDOC_INPUT_DELINS_START Function module of SAP. We triggered this logic by the search term of customer and reached the user exit where we had made some code changes. (User Exits are used to make code changes when we are running standard programs or reports or function modules). With this we were able to reach the desired point of calculating *** Issued and then find out the difference from Target *** Qty and get *** Qty Received for the scheduling agreement. We did not copy the standard function module into Z . Instead the same was done using a user exit.
<b>User exits in SD</b>
Menu Path:
SPRO- IMG- SD- System Modification- User Exists. User Exists are available in SD for the following processes:
User exits for price determination
User exits for partner determination
User exits for credit check & risk management
User exits in sales:
o User exits in sales doc processing
o User exits for contract processing
o User exits for product allocation processing
o User exits for availability checking
o User exits for component supply processing
o User exits for product selection
o User exits for billing plan
User exits for shipping
User exits for transportation
User exits for billing
User exits for general billing interface
User exits for sales support
User exits for lists.
The topic of user exits is a subject that concerns ABAP development & extensive experience in ABAP is required to understand and use the user exits.
A customer user exit is essentially a function module using a unique naming convention, in which set import and export parameters are defined to limit the data that can be manipulated. This is to protect certain data from being changed. This function module is attached to an enhancement that may contain other function modules. A user exit should only be used if the possibilities for customizing or application-specific user exits are inadequate.
NEW FIELDS IN PRICING:
To use a field in pricing, one creates a cond table. This cond table is created using the allowed fields from the field catalog. Should the fields one requires not be included in the list of allowed fields, one can add the fields from the list of available fields. However, one may find that a new field may not be in the list of available fields. For this reason, one must create new fields for pricing. The document & item data in SD is stored in data tables such as VBAK & VBAP (for the order transaction). Many of the fields from these tables are available in the field catalog.
The field catalog is a structure (KOMG) that consists of 2 tables (KOMK & KOMP). These tables contain the header & item data for pricing respectively. They are called KOMx because they are communications structures used to communicate the transaction data with the pricing procedure. Table KOMG contains the field KOMK & KOMP.
If you require a field that is not in KOMG, it means that it is not in KOMK or KOMP. This means that the field you require cannot be used in pricing because there is no communication of this field from the transaction to the pricing procedure via the communication structures.
To use a field not defined in the field catalog, you need to add this field to KOMK or KOMP structures, and then write the ABAP code to transfer the data in the field from the transaction tables to the communication structure. Follow these steps:
Create the field in the KOMK (header data) & KOMP (item data) tables using the standard includes provided for this requirement.
Write the code in the user exit to read the transaction data & transfer it to the KOMx structures.
Menu Path:
SPRO- IMG- SD- System Modification- Create New Fields (using the cond tech)- New fields for Pricing.
Adding the field to KOMK & KOMP:
This process requires some knowledge of the ABAP dictionary & how to use the ABAP dictionary to create & change fields & tables. If the field is from the header table (for e.g. the order table: VBAK), you will need to add it to the include table KOMKAZ in the table KOMK. If the field is from the item table (for e.g. the order item table: VBAP), you will need to add it to the include table KOMPAZ in table KOMP.
Lets say you need to use the base material to define a price & the base material is no in the pricing field catalog. The base material is a field on the MMR basic data screen & is defined as MARA-WRKST. Since this relates to the material, it is at the item level, so you would add the field to KOMKAZ include table.
When you add a field to these tables, it must start with ZZ. Therefore, the field you add would be ZZWRKST. In ABAP, when you add the field, use the same domain as in the field in the original table MARA-WRKST.
After adding the field, generate the structure KOMP. This field is not available in the field catalog & can be used in condition tables.
Menu Path:
SPRO- IMG- SD- System Modification- User Exists. User Exists are available in SD for the following processes:
User exits for price determination
User exits for partner determination
User exits for credit check & risk management
User exits in sales:
o User exits in sales doc processing
o User exits for contract processing
o User exits for product allocation processing
o User exits for availability checking
o User exits for component supply processing
o User exits for product selection
o User exits for billing plan
User exits for shipping
User exits for transportation
User exits for billing
User exits for general billing interface
User exits for sales support
User exits for lists.
The topic of user exits is a subject that concerns ABAP development & extensive experience in ABAP is required to understand and use the user exits.
A customer user exit is essentially a function module using a unique naming convention, in which set import and export parameters are defined to limit the data that can be manipulated. This is to protect certain data from being changed. This function module is attached to an enhancement that may contain other function modules. A user exit should only be used if the possibilities for customizing or application-specific user exits are inadequate.
NEW FIELDS IN PRICING:
To use a field in pricing, one creates a cond table. This cond table is created using the allowed fields from the field catalog. Should the fields one requires not be included in the list of allowed fields, one can add the fields from the list of available fields. However, one may find that a new field may not be in the list of available fields. For this reason, one must create new fields for pricing. The document & item data in SD is stored in data tables such as VBAK & VBAP (for the order transaction). Many of the fields from these tables are available in the field catalog.
The field catalog is a structure (KOMG) that consists of 2 tables (KOMK & KOMP). These tables contain the header & item data for pricing respectively. They are called KOMx because they are communications structures used to communicate the transaction data with the pricing procedure. Table KOMG contains the field KOMK & KOMP.
If you require a field that is not in KOMG, it means that it is not in KOMK or KOMP. This means that the field you require cannot be used in pricing because there is no communication of this field from the transaction to the pricing procedure via the communication structures.
To use a field not defined in the field catalog, you need to add this field to KOMK or KOMP structures, and then write the ABAP code to transfer the data in the field from the transaction tables to the communication structure. Follow these steps:
Create the field in the KOMK (header data) & KOMP (item data) tables using the standard includes provided for this requirement.
Write the code in the user exit to read the transaction data & transfer it to the KOMx structures.
Menu Path:
SPRO- IMG- SD- System Modification- Create New Fields (using the cond tech)- New fields for Pricing.
Adding the field to KOMK & KOMP:
This process requires some knowledge of the ABAP dictionary & how to use the ABAP dictionary to create & change fields & tables. If the field is from the header table (for e.g. the order table: VBAK), you will need to add it to the include table KOMKAZ in the table KOMK. If the field is from the item table (for e.g. the order item table: VBAP), you will need to add it to the include table KOMPAZ in table KOMP.
Lets say you need to use the base material to define a price & the base material is no in the pricing field catalog. The base material is a field on the MMR basic data screen & is defined as MARA-WRKST. Since this relates to the material, it is at the item level, so you would add the field to KOMKAZ include table.
When you add a field to these tables, it must start with ZZ. Therefore, the field you add would be ZZWRKST. In ABAP, when you add the field, use the same domain as in the field in the original table MARA-WRKST.
After adding the field, generate the structure KOMP. This field is not available in the field catalog & can be used in condition tables.
Pl reward if helpful.
Thanks
Sadhu Kishore

Create an invoice witout any reference of sales order

Hello
We have to create an invoice without sales order. If we try to use the BAPI BAPI_BILLINGDOC_CREATEMULTIPLE. We must give a Reference document.
How can we create the invoice without any sales orders and any reference. We have to do it by this way because the sales order is create into production and sales system and it's not SAP
Thanks for your help
Philippe
Helpful will award.

so why in the SAP help for the 4.7) they wrote:
<a href="http://help.sap.com/saphelp_46c/helpdata/en/dd/5615db545a11d1a7020000e829fd11/frameset.htm">SAP Help</a>
[quote]Until now, you could only use standard interfaces to bill orders and deliveries in the SAP system. With the general billing interface, you can now bill external business transactions.
Data from an external system to be used in your billing process must first be prepared in a sequential file of specified format.
All data necessary for billing can either be made available to you in this way or can be taken from existing master data. Material master data and pricing elements are not necessarily required in the system.
You may decide to work with a CpD customer master record instead of taking data (such as an address) from a customer master.
Pricing elements and/or VAT amounts can be transferred. Alternatively, you can carry out new pricing in billing, entirely or only for taxes.
You can also enter external reference numbers in the interface such as an external delivery or order number. When you create a billing document, the system records document flow using these reference numbers. This allows you to find a relevant billing document by entering an external reference number. Additionally, the system ensures that this number is billed only once. [/quote]
Thank for your help
Philippe

General Billing Interface

Similar Messages

Maybe you are looking for