sapnote_0001488901
3
21.05.2012 Page 1 of 3 SAP Note 1488901 - GR quantity more than the EI quantity can be referred- MIGO Note Language: English Version: 4 Validity: Valid Since 10.05.2011 Summary Symptom When excise invoice is captured in J1IEX and subsequently goods receipt is done in MIGO transaction, While carrying out goods receipt by referring the excise invoice captured, the checks are done perfectly and wrong postings are blocked through the note 1455670. But when a subsequent goods receipt(MIGO) is carried out where the quantity is equal to the total excise invoice quantity, the posting is not blocked. For e.g., an excise invoice is created for quantity 200 and a goods receipt is carried with quantity 100 referring the excise invoice. So, for subsequent GR, system should not allow quantity more than the remaining quantity which is 100 nos. This check is not managed and system allows to post the quantity 200 even second time. This issue occurs only when subsequent goods receipt is done for the exact total quantity of the excise invoice created. Also, while carrying out goods receipt for an Stock Transport order through SD route, system does not verify the excise invoice of sent plant in GR while referring outbound delivery in GR(MIGO). This note contains code corrections to validate the GR quantity while referring the excise invoice captured for all subsequent goods receipts. Also, takes care of validation of supplying plant's excise invoice for the delivery. Other terms LJ1IEXGMPAI, subroutine CHECK_EXNUM_EXDAT, refer excise invoice in MIGO, MIGO, GR qty more than EI qty, GR quantity, excise invoice quantity, Refer EI, refer excise invoice, Note 1305122, note . Reason and Prerequisites Reason: This problem is caused by a program error. Prerequisite Notes: 1407028, 1455670. Solution 1. Carryout the manual changes as present in the attachment 'message_class_328.zip'. A default warning message(4F-328) is displayed for STO scenarios and the message type can be changed as per customer requirement in the below path. SPRO => Logistics-General => Tax on Goods Movements => India => Tools => Message Control. 2. Implement the corrections relevant for your release. Header Data
-
Upload
murthy-magapu -
Category
Documents
-
view
8 -
download
0
Transcript of sapnote_0001488901
21.05.2012 Page 1 of 3
SAP Note 1488901 - GR quantity more than the EI quantitycan be referred- MIGO
Note Language: English Version: 4 Validity: Valid Since 10.05.2011
Summary
SymptomWhen excise invoice is captured in J1IEX and subsequently goods receipt isdone in MIGO transaction, While carrying out goods receipt by referring theexcise invoice captured, the checks are done perfectly and wrong postingsare blocked through the note 1455670.
But when a subsequent goods receipt(MIGO) is carried out where the quantityis equal to the total excise invoice quantity, the posting is not blocked.For e.g., an excise invoice is created for quantity 200 and a goods receiptis carried with quantity 100 referring the excise invoice. So, forsubsequent GR, system should not allow quantity more than the remainingquantity which is 100 nos. This check is not managed and system allows topost the quantity 200 even second time.
This issue occurs only when subsequent goods receipt is done for the exacttotal quantity of the excise invoice created.
Also, while carrying out goods receipt for an Stock Transport order throughSD route, system does not verify the excise invoice of sent plant in GRwhile referring outbound delivery in GR(MIGO).
This note contains code corrections to validate the GR quantity whilereferring the excise invoice captured for all subsequent goods receipts.Also, takes care of validation of supplying plant's excise invoice for thedelivery.
Other termsLJ1IEXGMPAI, subroutine CHECK_EXNUM_EXDAT, refer excise invoice in MIGO,MIGO, GR qty more than EI qty, GR quantity, excise invoice quantity, ReferEI, refer excise invoice, Note 1305122, note .
Reason and PrerequisitesReason: This problem is caused by a program error.Prerequisite Notes: 1407028, 1455670.
Solution1. Carryout the manual changes as present in the attachment 'message_class_328.zip'.
A default warning message(4F-328) is displayed for STO scenarios and themessage type can be changed as per customer requirement in the below path.
SPRO => Logistics-General => Tax on Goods Movements => India => Tools =>Message Control.
2. Implement the corrections relevant for your release.
Header Data
21.05.2012 Page 2 of 3
SAP Note 1488901 - GR quantity more than the EI quantitycan be referred- MIGO
Release Status: Released for CustomerReleased on: 10.05.2011 06:26:07Master Language: EnglishPriority: Correction with medium priorityCategory: Program errorPrimary Component: XX-CSC-IN-MM Materials Management
Secondary Components:XX-CSC-IN India
Valid Releases
Software Component Release FromRelease
ToRelease
andSubsequent
SAP_APPL 470 470 470
SAP_APPL 500 500 500
SAP_APPL 600 600 600
SAP_APPL 602 602 602
SAP_APPL 603 603 603
SAP_APPL 604 604 604
SAP_APPL 605 605 605
Support Packages
Support Packages Release Package Name
SAP_APPL 470 SAPKH47036
SAP_APPL 500 SAPKH50025
SAP_APPL 600 SAPKH60020
SAP_APPL 602 SAPKH60210
SAP_APPL 603 SAPKH60309
SAP_APPL 604 SAPKH60410
SAP_APPL 605 SAPKH60505
Related Notes
Number Short Text
1572603 Commercial invoice number & year not saved for imports- MIGO
1455670 GR quantity more than the EI quantity can be referred -MIGO
1407028 No excise invoice tab when batch mismatch in EI for STO-MIGO
Attachments
FileType
File Name Language Size
ZIP message_class_328.zip E 80 KB
Symptoms - Side-Effects
21.05.2012 Page 3 of 3
SAP Note 1488901 - GR quantity more than the EI quantitycan be referred- MIGO
The following SAP Notes correct this SAP Note / patch:
SAP NoteReason
Versionfrom
Versionto
SAP NoteSolution
Version SupportPackage
1488901 1572603 1
Correction Instructions
CorrectionInstructions
Validfrom
Validto
SoftwareComponent
Type*)
ReferenceCorrection
LastChanged
930012 600 600 SAP_APPL C P7DK193327 02.11.201015:10:38
994168 605 605 SAP_APPL C EB5K135598 10.05.201100:08:36
994169 604 604 SAP_APPL C E4AK132514 10.05.201100:14:14
994170 603 603 SAP_APPL C E38K133928 10.05.201100:49:41
994207 602 602 SAP_APPL C EACK117416 10.05.201101:12:45
994209 500 500 SAP_APPL C P6DK170828 10.05.201101:15:50
994210 470 470 SAP_APPL C P6BK308490 10.05.201101:20:26
*) C Correction, B Preprocessing, A Postprocessing, M Undefined Work
