Quality Notification Problem

[Former Member]

I am BAPI_QUALNOT_CREATE and BAPI_QUALNOT_SAVE for the Quality Notification(QA) Creation.

The QA is getting created but the Production Order is not getting updated on it.

I am getting the following message -

"Enter a production order or a production version"

Can someone give me some sample code or something and tell what I am not doing?

Thanks Archana.

[Former Member]

Hi Archana,

I am not sure whether it creates a Production Order or not...

Please check the documentation

*

Create QM Notification 2

Functionality

You can use this BAPI to create a new QM notification. You can create certain fields for the notification header, as well as items, causes, activities, and long texts for the notification. You can also maintain partner data.

Comments

Errors are transferred in the table RETURN.

The changes to the notification data will only be available on the database after the function modules BAPI_QUALNOT_SAVE and BAPI_TRANSACTION_COMMIT have run successfully.

Notes

The sort field must be filled if you want to create items, causes, tasks, or activities.

If you want to create a cause, the sort field for the item must also be filled.

The fields OBJTYP and OBJKEY must be filled when creating a long text. OBJTYP can contain the following values:

1. QMEL - Notification Header

2. QMFE - Notification Item

3. QMUR - Notification Cause

4. QMSM - Notification Task

5. QMMA - Notification Activity

OBJKEY must contain the corresponding sort field for the values listed above. The combination of sort fields for the item/cause, item/task, or item/activity must be unique within the notification. If you leave the sort field blank, and the OBJTYP is QMEL, a long text will be created for the notification header.

Example:

OBJTYP OBJKEY

QMEL initial (' ')

---> Long text for notification header

An external reference key can be transferred in the field REFOBJECTKEY. The relationships between external reference keys and SAP keys are transferred in the export table KEY_RELATIONSHIP. If the fields SENDER, REFOBJECTTYPE, and REFRELTYPE are filled, an object relationship can be created at notification header level.

Example: The reference object is a quality notification with the number

4711:

SENDER : Field "Logical System" from table T000

REFOBJECTTYPE : BUS2078

REFOBJECTKEY : 000000004711

REFRELTYPE : REFZ.

Sort number in the item:

If several items have the same sort number, you can assign a common cause and/or a common activity and/or a common task to these items.

Sort number in cause, activity, task:

The sort number is the key field for accessing the relevant cause, activity, or task.

A sort number for the item also exists in the cause, activity, and task. You can use this to sort causes, activities, and tasks at header or item level.

In the causes, the sort number for the item must be filled with a number that is greater than or equal to 1, because causes always belong to items and can never appear at header level. In activities and tasks, the sort number for the item can be zero; then these are part of the notification header.

Parameters

EXTERNAL_NUMBER

NOTIF_TYPE

NOTIFHEADER

TASK_DETERMINATION

SENDER

NOTIFHEADER_EXPORT

NOTITEM

NOTIFCAUS

NOTIFACTV

NOTIFTASK

NOTIFPARTNR

LONGTEXTS

KEY_RELATIONSHIPS

RETURN

Exceptions

Function Group

2078

*

Hope it helps...

Thanks,

Chaitanya