ISU_SCRIPT_INVOICE_POST_II

[Former Member]

Hi All,

I need to create a manual bill document (usually transaction EA16 is used) using the FM: : ISU_SCRIPT_INVOICE_POST_II.

Fields that are required for a manual bill include:

Rate Type

Billing Class

Stat. Rate

Quantity (SPs quantity, if present in the IDoc. A value of 0 if it is not included)

Billing Factor (always 1.0)

Unit of Measurement (depends on type of consumption, i.e. kWh, KW, RKVAH, or Therms, etc.)

Type of Quantity (always blank i.e. ‘no special specification’)

Weight Key (always 01)

Valid From Date (start date of the billing period)

Valid To date (end date of the billing period)

Sub transaction (Will be given by FICA)

Line Item Type (Z810CC and Z810AJ)

Pre-sorting (always 0002) etc

I am unable to map the fields listed above to the FM paramters….

Please help me in this regards and let me know if there is any other FM/BAPI to create a manual bill?

[Former Member]

Please use the BAPI *ISU_S_MANUBILL_CREATE*. This FM creates manual bill and the parameters required are same as EA16 transaction.

FUNCTION isu_s_manubill_create.

*"----

---

""Globale Schnittstelle:

*" IMPORTING

*" VALUE(X_VERTRAG) LIKE EVER-VERTRAG

*" VALUE(X_STICHTAG) LIKE REA16-STICHTAG OPTIONAL

*" VALUE(X_BUKRS) LIKE ERCH-BUKRS OPTIONAL

*" VALUE(X_SPARTE) LIKE ERCH-SPARTE OPTIONAL

*" VALUE(X_PROPRICE) LIKE REA16-PROPRICE OPTIONAL

*" VALUE(X_VBELNR) LIKE REA16-VBELNR OPTIONAL

*" VALUE(X_N_INVSEP) LIKE ERCH-N_INVSEP OPTIONAL

*" VALUE(X_CANCEL) LIKE REA16-CANCEL OPTIONAL

*" VALUE(X_TRANSFER) LIKE REA16-TRANSFER OPTIONAL

*" VALUE(X_UPD_ONLINE) LIKE REGEN-UPD_ONLINE OPTIONAL

*" REFERENCE(X_OBJ) TYPE ISU20_MANUBILL OPTIONAL

*" REFERENCE(X_DATA) TYPE ISU20_MANUBILL-DATA OPTIONAL

*" VALUE(X_NO_DIALOG) LIKE REGEN-NO_DIALOG OPTIONAL

*" REFERENCE(X_AUTO) TYPE ISU20_MANUBILL-AUTO OPTIONAL

*" EXPORTING

*" VALUE(Y_DB_UPDATE) LIKE REGEN-DB_UPDATE

*" VALUE(Y_EXIT_TYPE) LIKE REGEN-EXIT_TYPE

*" VALUE(Y_NEW_BILL_DOC) TYPE ISU2A_BILL_DOC

*" VALUE(Y_MSGID) TYPE MSGID

*" VALUE(Y_MSGNO) TYPE MSGNO

*" EXCEPTIONS

*" FOREIGN_LOCK

*" INPUT_ERROR

*" GENERAL_FAULT

*"----

---

I believe it will solve your issue.

[Former Member]

He had a problem with this function in version ECC 6.0 with an error message that was a warning, and we open a SAP message, and they answer:

"When you

are using the function module singly there exist no open protocol which

catches the messages. The system is writing the error directly on the

screen and aborts processing. In difference to that the transaction EA16is opening a protocol and because of that the message is raised

correctly.

Furthermore please notice that we do not recommend to use the function

modules marked with INTERNAL singly. They are designed just for internalusing and errors caused by it can not be handled by SAP."

and

"If a customer own program is really needed please use a protocol handling."

¿Do you know how use a use a protocol handling.?

Thanks in advance!!