Quantity field updation from MIGO to AUC to final asset.
Hi All
can anybody help me understand how the quantiy field is updated from MIGO having Internal Order which than settled to AUC form their to final asset.So that final asset has updated quantiy automatically.
Urgent help highly appriciated.
Thanks
hi
If you go to trx. ME23N with the PO number, please select the item and
double click. There you will see that field 'GR Non-valuated'.
When this field is marked, it implies that asset won't be affected by
the Goods receipt. Asset will be updated only when the invoice receipt
is posted. ie MIRO
Also, please refer to the following note for further information:-
44944 Quantity update in fixed asset with asset posting
In AS01/AS02, you will need to enter the unit of measure.
Best regards,
Blaz
Similar Messages
-
Quantity field updation in FBL1N
Hi,
Is it possible to bring the values to Quantity field in FBL1N?
If, so please suggest me how to proceed..
MPRHI,
if the quantities you are looking for are stored in the table fields BSEG-ERFMG, BSEG-BPMNG:
See SAPNET note 984305, how to add fields to FBL* reports.
Best regards, Christian -
GLT2201 error while settling AuC to Final Asset through KO88
Hello,
We have a scenario where in I am settliing an AuC through KO88 to the final Asset but am getting Document splitting error GLT2201. Profit Center is maintained in the Cost Center assigned to the Asset Master and also in the Internal Order. I could settle from the P/L account to the AuC asset when i ran KO88 earlier but its not allowing settling from AuC to the Final Asset.
We are using Parallel Ledger and I have defined 2 additional depreciation areas, 30 for posting only depreciation (real area) and 60 for posting only APC (derieved area). I have maintained ACSET for all the depreciation areas. I feel the error is due to Parallel Ledger but I am unable to figure out how and where.
Can anybody help me out please.
Thanks,
Rajat GuptaHello,
I managed to resolve the error, some how by oversight Profit Center was suppressed in the Field Status of Asset G/Ls though Cost Center was Optional. I changed the Profit Center Field Status to Optional and it worked.
But I am wondering how it allowed KO88 to run while settling from the Cost Element (P/L GL) to the AuC because they both used the same Field Status?
Thanks,
Rajat Gupta -
Need to settlem partial amount on AUC to final asset
Dear SAP Experts,
I would like to seek guidance on how we can allow partial settlement to final asset.
For example, we have an ongoing project/WBS that has been settled to AUC, for example 1000 EUR (i.e. as of end of period 1)
Our controlling area currency is USD and the project/WBS is set for Summary settlement only.
NOw, we want to settle 2000 EUR to a final asset in period 1 but retain the rest in AUC to be settled on a different final asset that is yet to be determined.
Here is the current setting of our settlement profile:
To be settled in fule - active
Indicators:
100% validation - active
% Settlement - active
Equivalence Numbers - active
Amount Settlement- Active
Appreciate any input you can provide
Thanks
AristotleHI,
1. System needs validity periods for manually entered distribution rules & you have from & to periods to specify. They need not be identical. You can specify a validity period which starts in April & ends in June, for example.
2. Combining the first & last lines of your latest post,
--You can execute Settlement multiple times within a period as long as you keep on posting costs after each settlement.
-- What is the minimum period for you to settle ideally (daily / weekly) ?
-- As SAP (also Business Processes in general) distinguishes between periods (months), you can do one time settlement each month to simplify & standardize your process. It has got the same effect even if you settle daily / weekly.
(FI & MM period closing are monthly, as you know).
-- If you want to do another settlement for the same asset in the same period & only the "%" changes, then you may create another distribution rule or you can comibine the "%" in one rule itself.
regards -
Problem with sales order update from MIGO ( using BADI)
I have written a BADI while doing MIGO, through which I am updating Sales order Order Quanity.
I am able to update the Quantity successfully in sales order, but I am getting following update termination message which is mentioned below.
"Sales Order 376446 has failed an update to the billing date associated to Transaction MIGO
Contact your STC Key user for assistance
PO Number:"
Any clue? Please suggest.
Regards,
Krishna Prasad MVNI have written a BADI while doing MIGO, through which I am updating Sales order Order Quanity.
I am able to update the Quantity successfully in sales order, but I am getting following update termination message which is mentioned below.
"Sales Order 376446 has failed an update to the billing date associated to Transaction MIGO
Contact your STC Key user for assistance
PO Number:"
Any clue? Please suggest.
Regards,
Krishna Prasad MVN -
Exit for PR fields updation from sc for Account assignment
Hi All,
I have a requirement where I need to update fields from Shopping Cart account assignment to Purchase requisiton customer data tab. could any one let me know how to make data flow from SC and make the data appear in PR.
ThanksHi,
Please check the BADI BBP_CREATE_BE_RQ_NEW.
Regards,
Masa -
Quantity field updated in asset master
Hi,
We are facing one problem when we are settling the WBS elements to AuC the settlement process is running fine but the original quantity mentioned in the asset master gets change after the settlement. to some X figure.
kindly help me to solve the problem, as it is not possible to go and edit the manually 100's of Asset master.
Points assured.
regards,
Anand DattaRefer the note 421308
Regards
Sreenivas -
Trouble after update from 4.1 RC2 to final 4.1
I get some trouble, look at these screenshots.. same shot, from v3 - 4 - r4.1rc1 - r4.1rc2 looks like always same results, with final 4.1 there'are some important differences..
Someone know why?
Im back to rc2 because of a lot of shots like this..
first screenshot
http://i48.tinypic.com/zn6md.jpg
second screenshot
http://i48.tinypic.com/657f5f.jpg
Perhaps the settings are misinterpreted in the final 4.1?
Same settings..
mac osx 10.6.8In 4.1 RC2, there was a problem with images containing large black areas when strong clarity was applied: http://feedback.photoshop.com/photoshop_family/topics/lightroom_4_1rc2_very_strange_behavi our_of_clarity_for_a_specific_image
It seems that your moon picture was affected by that bug and appeared to dark in 4.1 RC2. You apparently compensated for that by raising the shadows and blacks sliders.
In LR 4.1 final the problem was corrected, so your picture now appears with the correct overall brightness. And because of the increased shadows and blacks, you probably now see some extremely amplified camera noise in the dark areas. Unfortunately, you have to correct the shadows, blacks and possibly the exposure settings of this and all similar images.
P.S. This is just a guess - it could be some other problem, too. But the combination "large dark areas" and "strong clarity" fits the problem in the link very well. -
Quantity field not getting update in PCA document for Goods Receipt
We have the Purchase Account activated for our company code.
For movement type 101 (Goods Receipt), I am getting the quantity field updated for GR/IR account and Stock Account (B/S item).
But the quantity field is not getting updated for the "Purchase Account" and the "other offsetting PL A/C).
Please advice whether I am missing something.
Regards
B.MohantyHi Aravind,
Check SAP notes 1063198 and 1117587.
FAGLL03 display quantity which is updated in FAGLFLEXA, BSEG is not
relevant in this case. This is clearly explained in the note 1063198.
The quantity posts through to FI on the 'goods receipt' items, but not on the
'invoice receipt' items.
In the FI normally the Quantity is not a 'real' important field, as it
is more related to the MM area.
But in the old 'Profit Center Accounting' and the old' Special Ledger'
the field has been important.
As the same logic of these areas to 'store' the Quantity is also used
in the NewG/L the field get only filled in the line, where it make
'sense' from our point of view, because only in the 'goods receipt'
lines a 'real' Quantity is posted to the system.
So as before in the PCA and SL, now also in the NewG/L the Quantity is
filled in the correct and important lines and postings.
In the BSEG ('old document segment table') the field is filled 'just'
as it is send to the FI, but this is not completely correct from the
business point of view.
This can also lead to issues with the reporting and summation to this
field. So with creating the new logic in the NewG/L the 'correct'
standard of the 'writing' for the Quantity has also been taken over.
So in the end, the update and display is correct according SAP standard behavior.
Actually,Quantities within G/L are never reliable,
because the purpose of FI is a view on the data according to amount
but not according to quantity.
In the FI normally the Quantity is not a 'real' important field, as it
is more related to the MM area.
I hope I could be of assistance.
Regards,
Fernando -
Want "NOT to Default Quantity in GR from PO"
Hi,
My issue is, we want:
in MIGO> make GR Quantity field "Blank" instead of its getting copy from open PO quantity!
Most of the time user commits mistake when they received partial quantity,
(they save default open PO quantity ), We want to force user to TYPEIN actual receiving Quantity field while doing MIGO.
Any suggestion!
Thanks
-SamThe enhancement MEVME001 might be of help for you.
The documentation of this enhancement in transaction SMOD states that:
"The enhancement MEVME001 comprises the user exit EXIT_SAPLEINR_001,
which is invoked to calculate the default quantity in the case of a
goods receipt against a scheduling agreement.
Example:
If your vendors frequently deliver early, you can use this user exit
to specify that instead of the quantity open to date, the quantity
open up to the day after tomorrow is taken as the default quantity
for a goods receipt.
You can also specify that the tolerance check is to relate not to
the default quantity but to the total scheduled quantity.
This enhancement can be used to define the following data differently
to that in the standard system:
o Default quantity for goods receipt
In the standard system, the quantity open to date from the last-
transmitted SA release is used in the case of scheduling agreements
with release documentation (document type LPA). In the case of
scheduling agreements without release documentation (document type
LP), the open quantity to date is used.
Note
If you use vendor confirmations with GR assignment, the quantity
from the confirmation is suggested (i.e. in this case, the default
quantity cannot be influenced via the user exit.
o The quantity to which the tolerance calculation is to relate
(In the standard system, the tolerance check relates to the default
quantity - i.e. the quantity open to date). At the time of the
tolerance check, the tolerance limits for under- and overdeliveries
entered in the scheduling agreement item are taken into account.
The parameters F1 and F2 are passed on in the interface to the user
exit. These parameters must contain the following data:
Parameter F1
= Default quantity + total of all already delivered quantities (posted
GR quantity)
(The already delivered quantity is deducted again prior to the output
of the default quantity on the screen.)
Parameter F2
= Quantity to which the tolerance calculation relates
All schedule lines for the relevant item are passed on in the internal
table "CETT" as the basis for determining the default quantity and the
tolerance.
Note
Please note that the user exit applies to both document types."
Please, check also the information contained under the two attached
notes:
874264 - MB01/MIGO: Default quantity for goods receipt posting
105169 - Default quntity durng goods receipt f.purchase ordr
Hope this will help.
Regards,
Sunitha. -
Quantity field in at user-command
Hi,
I have declared the quantity field V_QTY TYPE AFKO-GAMNG.
I am passing the quantity field values from the internal table which is having data for the quantity field to V_QTY. but the field V_QTY is not filling with the quantity.
Instead of the quantity, it is taking the * value into the field.
I am not using any control break commands in my coding. I am attaching the code also. can anyone guide me .
Report ztest.
TABLES: AFKO, " Order Header
AFPO, " Order Item
AUFK, " Order Master
RESB,
AFVC, " Order Operation w/i an Order
AFVV, " Qty/Dates/values in an Operation
CRHD, " Work Center
MARA, " Material Master
MAKT, " Material Description
AUSP, " Characteristic Values
CABN, " Characteristic
PLPO, " Task list-operation/activity
PLFL, " Task list - sequences
TJ02T, " System status texts
JEST. " Individual Object Status
TYPE-POOLS:SLIS.
TYPE-POOLS:ICON.
DATA:CHECK(1),
TOTAL(7) VALUE 'TOTAL :',
W_AMOUNT TYPE GAMNG VALUE 0.
TYPES:BEGIN OF T_AFKO,
CHECK,
AUFNR TYPE AFKO-AUFNR,
GLTRP TYPE AFKO-GLTRP,
GSTRP TYPE AFKO-GSTRP,
GAMNG TYPE AFKO-GAMNG,
PLNBEZ TYPE AFKO-PLNBEZ,
END OF T_AFKO.
DATA:I_AFKO TYPE STANDARD TABLE OF T_AFKO,
W_AFKO LIKE LINE OF I_AFKO.
DATA:I_AFKO1 TYPE STANDARD TABLE OF T_AFKO,
W_AFKO1 LIKE LINE OF I_AFKO1.
DATA:PONUM TYPE AFKO-AUFNR,
STDATE TYPE AFKO-GLTRP,
FIDATE TYPE AFKO-GSTRP,
QUANTY TYPE AFKO-GAMNG,
MATER TYPE AFKO-PLNBEZ,
DESCR TYPE MAKT-MAKTX,
INDEX TYPE SY-INDEX,
COUNT(3) VALUE '0'.
TYPES:BEGIN OF T_FINAL,
CHECK,
LIGHT TYPE ICON-ID,
MATNR TYPE RESB-MATNR,
AUFNR TYPE AFKO-AUFNR,
GLTRP TYPE AFKO-GLTRP,
GSTRP TYPE AFKO-GSTRP,
GAMNG TYPE AFKO-GAMNG,
PLNBEZ TYPE AFKO-PLNBEZ,
MAKTX TYPE MAKT-MAKTX,
END OF T_FINAL.
DATA:I_FINAL TYPE STANDARD TABLE OF T_FINAL,
W_FINAL LIKE LINE OF I_FINAL,
I_FINAL1 TYPE STANDARD TABLE OF T_FINAL,
W_FINAL1 LIKE LINE OF I_FINAL1.
TYPES:BEGIN OF T_CRHD,
OBJID TYPE CRHD-OBJID,
ARBPL TYPE CRHD-ARBPL,
END OF T_CRHD.
DATA:I_CRHD TYPE STANDARD TABLE OF T_CRHD,
W_CRHD LIKE LINE OF I_CRHD.
TYPES:BEGIN OF T_AFVC,
AUFPL TYPE AFVC-AUFPL,
ARBID TYPE AFVC-ARBID,
END OF T_AFVC.
DATA:I_AFVC TYPE STANDARD TABLE OF T_AFVC,
W_AFVC LIKE LINE OF I_AFVC.
TYPES:BEGIN OF T_ITEM,
MATNR TYPE RESB-MATNR, " Component Matl Number
MAKTX TYPE MAKT-MAKTX, " Matl Desc for Component
BDMNG TYPE RESB-BDMNG, " Component Req'd Qty
END OF T_ITEM.
DATA:I_ITEM TYPE STANDARD TABLE OF T_ITEM,
W_ITEM LIKE LINE OF I_ITEM.
TYPES:BEGIN OF T_RESB,
MATNR TYPE RESB-MATNR,
AUFNR TYPE RESB-AUFNR,
BDMNG TYPE RESB-BDMNG,
END OF T_RESB.
DATA:I_RESB TYPE STANDARD TABLE OF T_RESB,
W_RESB LIKE LINE OF I_RESB.
DATA:I_MAKT TYPE STANDARD TABLE OF MAKT,
W_MAKT LIKE LINE OF I_MAKT,
I_MAKT1 TYPE STANDARD TABLE OF MAKT,
W_MAKT1 LIKE LINE OF I_MAKT1.
TYPES:BEGIN OF T_AUFK,
AUFNR TYPE AUFK-AUFNR,
AUART TYPE AUFK-AUART,
WERKS TYPE AUFK-WERKS,
OBJNR TYPE AUFK-OBJNR,
END OF T_AUFK.
DATA:I_JEST TYPE STANDARD TABLE OF JEST,
W_JEST LIKE LINE OF I_JEST.
DATA:I_AUFK TYPE STANDARD TABLE OF T_AUFK,
W_AUFK LIKE LINE OF I_AUFK.
DATA:V_QTY TYPE AFKO-GAMNG,
LINES TYPE I,
V_AUFNR TYPE AFKO-AUFNR.
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.
PARAMETERS:
P_WERKS TYPE AUFK-WERKS OBLIGATORY MEMORY ID WRK, " PLANT
P_AUART TYPE AUFK-AUART OBLIGATORY. "ORDER TYPE
SELECT-OPTIONS: S_PLNBEZ FOR AFKO-PLNBEZ. "material
PARAMETERS: P_ARBPL TYPE CRHD-ARBPL OBLIGATORY. "Work center
SELECT-OPTIONS:
S_GSTRP FOR AFKO-GSTRP OBLIGATORY. "ORDER BASIC START DATE
*s_gltrp FOR afko-gltrp OBLIGATORY, "ORDER BASIC FINISH DATE
*s_gstrs FOR afko-gstrs, "ORDER SCHEDULE START DATE
*s_gltrs FOR afko-gltrs. "ORDER SCHEDULE FINISH DATE
PARAMETERS:P_MATNR TYPE RESB-MATNR.
SELECTION-SCREEN END OF BLOCK B1.
*ALV data declarations
DATA: I_FIELDCATALOG TYPE SLIS_T_FIELDCAT_ALV,
W_FIELDCATALOG LIKE LINE OF I_FIELDCATALOG,
S_FIELDCATALOG TYPE SLIS_T_FIELDCAT_ALV WITH HEADER LINE,
GD_TAB_GROUP TYPE SLIS_T_SP_GROUP_ALV,
GD_LAYOUT TYPE SLIS_LAYOUT_ALV,
GD_REPID LIKE SY-REPID VALUE SY-REPID,
T_HEADING TYPE SLIS_T_LISTHEADER,
IT_LISTHEADER TYPE SLIS_T_LISTHEADER,
W_KEYINFO TYPE SLIS_KEYINFO_ALV,
WA_SORT TYPE SLIS_SORTINFO_ALV,
IT_SORT TYPE SLIS_T_SORTINFO_ALV,
IT_TITLE_BASIC TYPE
LVC_TITLE VALUE 'SELECTION OF PRODUCTION ORDERS',
IT_TITLE_ITEM TYPE LVC_TITLE VALUE 'MIXING REPORT'.
DATA: PO TYPE AUFNR,
P_SELFIELD TYPE SLIS_SELFIELD.
DATA: I_EVENTS TYPE SLIS_T_EVENT,
W_EVENTS LIKE LINE OF I_EVENTS.
CLEAR: W_EVENTS.
REFRESH: I_EVENTS.
DATA:I_HEADER TYPE SLIS_T_LISTHEADER,
W_HEADER LIKE LINE OF I_HEADER.
BEGIN OF CODE FOR ALV_HIERSEQ_LIST*************
TYPES:BEGIN OF T_HHEADER,
EXPAND,
MATNR TYPE RESB-MATNR,
MAKTX TYPE MAKT-MAKTX,
V_QTY,
END OF T_HHEADER.
DATA:I_HHEADER TYPE STANDARD TABLE OF T_HHEADER,
W_HHEADER LIKE LINE OF I_HHEADER.
TYPES:BEGIN OF T_HITEM,
CHECK,
MATNR TYPE RESB-MATNR,
AUFNR TYPE AFKO-AUFNR,
GAMNG TYPE AFKO-GAMNG,
PLNBEZ TYPE AFKO-PLNBEZ,
MAKTX TYPE MAKT-MAKTX,
GLTRP TYPE AFKO-GLTRP,
GSTRP TYPE AFKO-GSTRP,
END OF T_HITEM.
DATA:I_HITEM TYPE STANDARD TABLE OF T_HITEM,
W_HITEM LIKE LINE OF I_HITEM.
END OF CODE FOR ALV_HIERSEQ_LIST ****************************
INITIALIZATION.
PERFORM BUILD_FIELDCATALOG.
PERFORM BUILD_LAYOUT.
*Start-of-selection.
START-OF-SELECTION.
PERFORM GET_EVENTS.
PERFORM GET_DATA.
END-OF-SELECTION.
PERFORM DISPLAY_ALV_REPORT.
*& Form BUILD_FIELDCATALOG
text
FORM BUILD_FIELDCATALOG.
CLEAR W_FIELDCATALOG .
W_FIELDCATALOG-COL_POS = '1'.
W_FIELDCATALOG-FIELDNAME = 'MATNR'.
W_FIELDCATALOG-TABNAME = 'I_HHEADER'.
W_FIELDCATALOG-SELTEXT_M = 'Phantom Material'.
W_FIELDCATALOG-ROLLNAME = 'MATNR'.
W_FIELDCATALOG-OUTPUTLEN = '20'.
APPEND W_FIELDCATALOG TO I_FIELDCATALOG.
CLEAR W_FIELDCATALOG .
W_FIELDCATALOG-COL_POS = '2'.
W_FIELDCATALOG-FIELDNAME = 'MAKTX'.
W_FIELDCATALOG-TABNAME = 'I_HHEADER'.
W_FIELDCATALOG-SELTEXT_M = 'Phantom Material Description'.
W_FIELDCATALOG-ROLLNAME = 'MAKTX'.
W_FIELDCATALOG-OUTPUTLEN = '40'.
APPEND W_FIELDCATALOG TO I_FIELDCATALOG.
CLEAR W_FIELDCATALOG .
W_FIELDCATALOG-COL_POS = '3'.
W_FIELDCATALOG-FIELDNAME = 'BDMNG'.
W_FIELDCATALOG-TABNAME = 'I_HHEADER'.
W_FIELDCATALOG-OUTPUTLEN = '20'.
W_FIELDCATALOG-SELTEXT_M = 'Total Batch qty:'.
APPEND W_FIELDCATALOG TO I_FIELDCATALOG.
CLEAR W_FIELDCATALOG .
W_FIELDCATALOG-COL_POS = '1'.
W_FIELDCATALOG-SELTEXT_M = 'Selection'.
W_FIELDCATALOG-FIELDNAME = 'CHECK'.
W_FIELDCATALOG-TABNAME = 'I_HITEM'.
W_FIELDCATALOG-EDIT = 'X'.
W_FIELDCATALOG-CHECKBOX = 'X'.
W_FIELDCATALOG-INPUT = 'X'.
W_FIELDCATALOG-HOTSPOT = 'X'.
APPEND W_FIELDCATALOG TO I_FIELDCATALOG.
CLEAR W_FIELDCATALOG .
W_FIELDCATALOG-COL_POS = '2'.
W_FIELDCATALOG-FIELDNAME = 'MATNR'.
W_FIELDCATALOG-TABNAME = 'I_HITEM'.
W_FIELDCATALOG-ROLLNAME = 'MATNR'.
W_FIELDCATALOG-OUTPUTLEN = '12'.
APPEND W_FIELDCATALOG TO I_FIELDCATALOG.
CLEAR W_FIELDCATALOG .
W_FIELDCATALOG-COL_POS = '2'.
W_FIELDCATALOG-FIELDNAME = 'AUFNR'.
W_FIELDCATALOG-TABNAME = 'I_HITEM'.
W_FIELDCATALOG-ROLLNAME = 'AUFNR'.
W_FIELDCATALOG-OUTPUTLEN = '12'.
APPEND W_FIELDCATALOG TO I_FIELDCATALOG.
CLEAR W_FIELDCATALOG.
W_FIELDCATALOG-COL_POS = '3'.
W_FIELDCATALOG-SELTEXT_M = 'PO Qty'.
W_FIELDCATALOG-FIELDNAME = 'GAMNG'.
W_FIELDCATALOG-ROLLNAME = 'GAMNG'.
W_FIELDCATALOG-OUTPUTLEN = '20'.
W_FIELDCATALOG-TABNAME = 'I_HITEM'.
APPEND W_FIELDCATALOG TO I_FIELDCATALOG.
CLEAR W_FIELDCATALOG.
W_FIELDCATALOG-COL_POS = '4'.
W_FIELDCATALOG-SELTEXT_M = 'Header Material'.
W_FIELDCATALOG-FIELDNAME = 'PLNBEZ'.
W_FIELDCATALOG-ROLLNAME = 'MATNR'.
W_FIELDCATALOG-OUTPUTLEN = '20'.
W_FIELDCATALOG-TABNAME = 'I_HITEM'.
APPEND W_FIELDCATALOG TO I_FIELDCATALOG.
CLEAR W_FIELDCATALOG.
W_FIELDCATALOG-COL_POS = '5'.
W_FIELDCATALOG-SELTEXT_M = 'Material Description'.
W_FIELDCATALOG-FIELDNAME = 'MAKTX'.
W_FIELDCATALOG-ROLLNAME = 'MAKTX'.
W_FIELDCATALOG-OUTPUTLEN = '40'.
W_FIELDCATALOG-TABNAME = 'I_HITEM'.
APPEND W_FIELDCATALOG TO I_FIELDCATALOG.
CLEAR W_FIELDCATALOG .
W_FIELDCATALOG-COL_POS = '6'.
W_FIELDCATALOG-FIELDNAME = 'GSTRP'.
W_FIELDCATALOG-TABNAME = 'I_HITEM'.
W_FIELDCATALOG-ROLLNAME = 'CO_GSTRP'.
W_FIELDCATALOG-OUTPUTLEN = '10'.
APPEND W_FIELDCATALOG TO I_FIELDCATALOG.
CLEAR W_FIELDCATALOG .
W_FIELDCATALOG-COL_POS = '7'.
W_FIELDCATALOG-FIELDNAME = 'GLTRP'.
W_FIELDCATALOG-TABNAME = 'I_HITEM'.
W_FIELDCATALOG-ROLLNAME = 'CO_GLTRP'.
W_FIELDCATALOG-OUTPUTLEN = '10'.
W_FIELDCATALOG-SELTEXT_M = 'Basic End Date'.
APPEND W_FIELDCATALOG TO I_FIELDCATALOG.
ENDFORM. "BUILD_FIELDCATALOG
*& Form get_events
text
FORM GET_EVENTS.
CLEAR : W_EVENTS, I_EVENTS[].
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
EXPORTING
I_LIST_TYPE = 0
IMPORTING
ET_EVENTS = I_EVENTS.
READ TABLE I_EVENTS WITH KEY NAME = SLIS_EV_TOP_OF_PAGE
INTO W_EVENTS.
IF SY-SUBRC EQ 0.
MOVE 'TOP_OF_PAGE' TO W_EVENTS-FORM.
MODIFY I_EVENTS FROM W_EVENTS INDEX SY-TABIX.
ENDIF.
READ TABLE I_EVENTS WITH KEY NAME = SLIS_EV_USER_COMMAND
INTO W_EVENTS.
IF SY-SUBRC EQ 0.
MOVE 'SUB_USER_COMMAND' TO W_EVENTS-FORM.
MODIFY I_EVENTS FROM W_EVENTS INDEX SY-TABIX.
ENDIF.
READ TABLE I_EVENTS WITH KEY NAME = SLIS_EV_PF_STATUS_SET
INTO W_EVENTS.
IF SY-SUBRC EQ 0.
MOVE 'PF_STATUS_SET' TO W_EVENTS-FORM.
MODIFY I_EVENTS FROM W_EVENTS INDEX SY-TABIX.
ENDIF.
ENDFORM. "get_events
*& Form build_layout
text
FORM BUILD_LAYOUT.
gd_layout-no_input = 'X'.
gd_layout-colwidth_optimize = 'X'.
GD_LAYOUT-ZEBRA = 'X'.
W_KEYINFO-HEADER01 = 'MATNR'.
W_KEYINFO-ITEM01 = 'MATNR'.
GD_LAYOUT-TOTALS_TEXT = 'Totals'(201).
GD_LAYOUT-EXPAND_FIELDNAME = 'EXPAND'.
ENDFORM. " BUILD_LAYOUT
*& Form data_retrieval
text
FORM GET_DATA.
IF p_matnr IS NOT INITIAL.
SELECT MATNR
AUFNR
BDMNG
FROM RESB INTO TABLE I_RESB
WHERE DUMPS = 'X'.
AND matnr = p_matnr.
SORT I_RESB BY MATNR AUFNR.
ENDIF.
SELECT * FROM JEST INTO CORRESPONDING FIELDS OF TABLE I_JEST
WHERE STAT = 'I0002'
AND INACT = ' '.
SELECT OBJID
ARBPL
FROM CRHD INTO TABLE I_CRHD WHERE ARBPL = P_ARBPL.
IF NOT I_CRHD[] IS INITIAL.
SELECT AUFPL
ARBID
FROM AFVC INTO TABLE I_AFVC
FOR ALL ENTRIES IN I_CRHD
WHERE ARBID = I_CRHD-OBJID.
ENDIF.
IF NOT I_AFVC[] IS INITIAL.
SELECT AUFNR
GLTRP
GSTRP
GAMNG
PLNBEZ
FROM AFKO INTO CORRESPONDING FIELDS OF TABLE I_AFKO
FOR ALL ENTRIES IN I_AFVC
WHERE AUFPL = I_AFVC-AUFPL
AND GSTRP IN S_GSTRP.
SORT I_AFKO BY AUFNR.
ENDIF.
IF NOT I_AFKO[] IS INITIAL.
SELECT AUFNR
AUART
WERKS
OBJNR
FROM AUFK INTO TABLE I_AUFK
FOR ALL ENTRIES IN I_AFKO
WHERE AUFNR = I_AFKO-AUFNR
AND AUART = P_AUART
AND WERKS = P_WERKS.
SORT I_AUFK BY AUFNR OBJNR.
SELECT * FROM MAKT INTO TABLE I_MAKT1
FOR ALL ENTRIES IN I_AFKO
WHERE MATNR = I_AFKO-PLNBEZ
AND SPRAS = SY-LANGU.
SORT I_MAKT1 BY MATNR.
ENDIF.
IF NOT I_RESB[] IS INITIAL.
SELECT * FROM MAKT INTO TABLE I_MAKT
FOR ALL ENTRIES IN I_RESB
WHERE MATNR = I_RESB-MATNR
AND SPRAS = SY-LANGU.
SORT I_MAKT BY MATNR.
ENDIF.
CLEAR W_HHEADER-BDMNG.
***BEGIN OF PHANTOM MATERIAL HEADER INTERNAL TABLE***
CLEAR W_AUFK.
CLEAR W_RESB.
LOOP AT I_RESB INTO W_RESB.
W_HHEADER-MATNR = W_RESB-MATNR.
READ TABLE I_MAKT INTO W_MAKT
WITH KEY MATNR = W_RESB-MATNR BINARY SEARCH.
W_HHEADER-MAKTX = W_MAKT-MAKTX.
APPEND W_HHEADER TO I_HHEADER.
MODIFY I_HHEADER FROM W_HHEADER INDEX SY-TABIX.
CLEAR W_HHEADER.
CLEAR W_RESB.
SORT I_HHEADER BY MATNR.
DELETE ADJACENT DUPLICATES FROM I_HHEADER.
ENDLOOP.
****END OF PHANTOM MATERIAL HEADER INTERNAL TABLE***
**BEGIN OF PHANTOM MATERIAL ITEM DETAILS***************
IF NOT I_HHEADER[] IS INITIAL.
LOOP AT I_HHEADER INTO W_HHEADER.
LOOP AT I_RESB INTO W_RESB WHERE MATNR = W_HHEADER-MATNR.
IF SY-SUBRC = 0.
READ TABLE I_AUFK INTO W_AUFK
WITH KEY AUFNR = W_RESB-AUFNR.
READ TABLE I_JEST INTO W_JEST
WITH KEY OBJNR = W_AUFK-OBJNR.
IF SY-SUBRC = 0.
W_HITEM-CHECK = CHECK.
W_HITEM-MATNR = W_HHEADER-MATNR.
READ TABLE I_AFKO INTO W_AFKO
WITH KEY AUFNR = W_AUFK-AUFNR BINARY SEARCH.
W_HITEM-AUFNR = W_AFKO-AUFNR.
W_HITEM-PLNBEZ = W_AFKO-PLNBEZ.
READ TABLE I_MAKT1 INTO W_MAKT1
WITH KEY MATNR = W_AFKO-PLNBEZ.
W_HITEM-MAKTX = W_MAKT1-MAKTX.
W_HITEM-GLTRP = W_AFKO-GLTRP.
W_HITEM-GSTRP = W_AFKO-GSTRP.
W_HITEM-GAMNG = W_AFKO-GAMNG.
APPEND W_HITEM TO I_HITEM.
MODIFY I_HITEM FROM W_HITEM INDEX SY-TABIX.
SORT I_HITEM BY AUFNR.
CLEAR W_HITEM.
ENDIF.
ENDIF.
ENDLOOP.
ENDLOOP.
ENDIF.
***********END OF PHANTOM MATERIAL ITEM DETAILS.*********************
ENDFORM. "get_item_DETAILS
*& Form top_of_page
text
FORM TOP_OF_PAGE.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
IT_LIST_COMMENTARY = I_HEADER
I_LOGO =
I_END_OF_LIST_GRID =
ENDFORM. " alv_top_of_page
*& Form user_command
text
-->P_UCOMM text
-->P_SELFIELD text
FORM DISPLAY_ALV_REPORT.
SORT I_HHEADER BY MATNR.
SORT I_HITEM BY MATNR AUFNR.
CALL FUNCTION 'REUSE_ALV_HIERSEQ_LIST_DISPLAY'
EXPORTING
I_INTERFACE_CHECK = ' '
I_CALLBACK_PROGRAM = GD_REPID
I_CALLBACK_PF_STATUS_SET = 'PF_STATUS_SET'
I_CALLBACK_USER_COMMAND = 'SUB_USER_COMMAND'
IS_LAYOUT = GD_LAYOUT
IT_FIELDCAT = I_FIELDCATALOG
IT_EXCLUDING =
IT_SPECIAL_GROUPS =
IT_SORT =
IT_FILTER =
IS_SEL_HIDE =
I_SCREEN_START_COLUMN = 0
I_SCREEN_START_LINE = 0
I_SCREEN_END_COLUMN = 0
I_SCREEN_END_LINE = 0
I_DEFAULT = 'X'
I_SAVE = ' '
IS_VARIANT =
IT_EVENTS = I_EVENTS[]
IT_EVENT_EXIT =
I_TABNAME_HEADER = 'I_HHEADER'
I_TABNAME_ITEM = 'I_HITEM'
i_structure_name_header =
i_structure_name_item =
IS_KEYINFO = W_KEYINFO
IS_PRINT =
IS_REPREP_ID =
I_BYPASSING_BUFFER =
I_BUFFER_ACTIVE =
IMPORTING
E_EXIT_CAUSED_BY_CALLER =
ES_EXIT_CAUSED_BY_USER =
TABLES
T_OUTTAB_HEADER = I_HHEADER
T_OUTTAB_ITEM = I_HITEM
EXCEPTIONS
PROGRAM_ERROR = 1
OTHERS = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. "display_alv_report
*****BEGIN OF CUMMILATIVE QUANTITY***********************
FORM PF_STATUS_SET USING EXTAB TYPE SLIS_T_EXTAB.
BREAK POINT.
SET PF-STATUS 'STANDARD' EXCLUDING EXTAB.
ENDFORM. "PF_STATUS_SET
*& Form SUB_USEMR_COMMAND
text
-->P_UCOMM text
-->P_SELFIELD text
FORM SUB_USER_COMMAND USING P_UCOMM LIKE SY-UCOMM
P_SELFIELD TYPE SLIS_SELFIELD.
CASE SY-UCOMM.
WHEN 'SUMM'.
CLEAR W_HITEM.
CLEAR W_HHEADER-V_QTY.
P_SELFIELD-REFRESH = 'X'.
DATA:LV_TABIX TYPE SY-TABIX.
LOOP AT I_HITEM INTO W_HITEM.
READ TABLE I_HHEADER INTO W_HHEADER
WITH KEY MATNR = W_HITEM-MATNR BINARY SEARCH.
IF SY-SUBRC = 0.
LV_TABIX = SY-TABIX.
IF W_HITEM-CHECK = 'X'.
W_HHEADER-V_QTY = W_HHEADER-V_QTY + W_HITEM-GAMNG.
MODIFY I_HHEADER FROM W_HHEADER
INDEX LV_TABIX." TRANSPORTING V_QTY.
ENDIF.
ENDIF.
ENDLOOP.
ENDCASE.
ENDFORM. "USER_COMMAND
*********END OF CUMMILATIVE QUANTITY
Thanks in advance.
Ramesh.Hello Ramesh,
Check your declerations,
In internal table I_HHEADER , the quantity field is of character type. And in internal table I_HITEM, the field GAMNG is of type quantity. There will be type mismatch.Correct it and see if it works.
Regards -
Possible bug? Nested tables and quantity fields in the nested table.
Hey guys,
I have witnessed a weird bug, maybe someone can clarify this for me.
1. Create a nested table. The inner table contains a quantity field of type DZIEME (FROM VBAP-ZIEME).
2. Create your interface and just put this table in the import section. Try to activate. It will work.
3. Create an adobe form for it and a program and execute it. You'll get a short dump saying that VBAP-ZIEME is unknown and that there are errors in the dynamically generated function.
Second test.
1. Create a nested table. The outer table contains a quantity field of type DZIEME (FROM VBAP-ZIEME).
2. Create your interface and just put this table in the import section. Try to activate. It will NOT work.
You have to make the addition of the quantity fields in Currency/Quantity Fields.
From this I see that the checker, doesn't look into nested tables for quantity/currency fields and just activates the interface.
Third test
1. Create a nested table. The inner table contains a quantity field of type DZIEME (FROM VBAP-ZIEME).
2. Create your interface:
2.a. Put this table in the import section.
2.b. Declare the nested Quantity field in the Currency/Quantity Fields section, using the autofiller (the buttons to the right of the field)
2.c Try to activate. It will work.
3. Create an adobe form for it and a program and execute it. You'll get a short dump which for some reason has no info.
From this, I understand that the Currency/Quantity Fields section may not declare the quantity fields, from nested tables, correctly.
What do you guys think? What am I doing wrong?
Thanks,@Anne Kathrine P...
By nested tables I mean creating table types, in the dictionary (se11) then in the interface>Import section adding a parameter X TYPE B_T.
i.e.
Structure A
Table type of structure A, A_T
Structure B containing a field of table type A
Table type B of structure B, B_T.
The issue can be easily solved for Z tables by changing the component type from quantity to decimal type. -
MACOS X ML: update from DP4 to release version
is it possible to update from developer preview 4 to final release version bought via appstore? it keeps telling me I already have it installed!
Ignore the message and proceed anyways. You won´t see any problem.
-
Will Project Budget be available again after settlement to AUC/final asset?
I would like to know if my project budget will become available again once I settle costs to AUC and to Final asset (or settle directly to final asset w/o AUC).
Letu2019s say my original budget for WBS is 5000, cost was posted to the WBS u2013 4000, now I settle the 4000 cost to AUC (and eventually from AUC to final asset). Will this mean the entire 5000 will be available again since the cost has been settled from WBS to AUC (and eventually fixed asset)?
Thanks!
VivianIf you have Budgeted WBS element and than after you does any cost postings against that WBS. you budget get consumed by that actual cost.
however, WBS element is capturing cost for the period of project duration that cost has to transfer to FI/ CO , finally so, at the period-end we does the settlement & transfer taht cost to cost center , PA , asset etc....
So, no point that after settlement your budget will be your initial budget.
Regards
Nitin -
WBS element is updated while settling cost from WBS to AUC
Hi Experts
At the time of settlement , when we settling the cost from WBS to AUC , WBS element is updated in AUC line item of accounting document , but it should not be updated actually.
As result AUC cost is loaded on WBS and budget of WBS is get affected , furthermore system is not allowing for MIGO even budget is available but in CJ30 it is showing assigned value is more then original budget.
Please suggest.
Thanks & Regards
shaileshHi Saurabh ,
I totally agree with you , but in our case system is not allowing(Error Message: Budget Exceeded) MIGO against capex PO - > WBS.
Note : in our case , system is checking budget at the time of MIGO also.
in our case , report S_ALR_87013558 is showing wrong actual value and also in CJ30 , total assigned value is larger then total distributable budget , As result our available budget gets negative figure in report S_ALR_87013558 , even i have already run CJEN->CJBN 2 or 3 times.
Note: Our Commitment value is correct.
Actually , according to report S_ALR_87013542 , system is showing correct actual value , that means we have sufficient available budget for further MIGO's
Now may be , due to WBS element is updated in AUC line item of accouning document of settlement (WBS to AUC) , system loads AUC values to WBS unnecessarily , our available budget gets negative figure.
For your reference , i am attaching screen shot of accounting document which is generated at the time of settlement from WBS to AUC.
Maybe you are looking for
-
I bought an iPad and opened up an iCloud account now iCloud won't register my new email address on my iPad! Why?
-
Error CX_SY_CONVERSION_NO_DATE_TIME with value 99991231 when calling a WS
I'm calling a Web Service in a SAP system from an external program which is written in Java. I got exception CX_SY_CONVERSION_NO_DATE_TIME when I tried to pass value 99991231 to a date field Bapie1Maw1Rt-ListStTo. Do you know other workarounds for th
-
I am new in the java world. I have a problem trying to get my little program work. I wrote a code to get the range of some values as public int getRange() { int range = 0; for (int i = 0; i < iArray.length; i++;) { range += (max, min); return max - m
-
From where the systeme proposes the Delivery date in the PO
Dear All, Please let me know from where the Delivery date gets proposed in the PO? It is not releated to the MRP views parameters, isn't it? Regards Ahmad
-
Can't open Photoshop CC. "could not initialize photoshop because of a program error"
What's the latest fix-it for this. Many of you have the same issue but there are so many different answers. Confusing (especially since I am a novice at this).