GR via MIGO allowed for POs with conf control key

GR via MIGO allowed for POs with conf control key.
where GRs should be allowed only based on ASN (INB) Del.
How to restrict GR via MIGO when confirmation control key is set?

ideally it should work, however check Conformation Control Key LA.
Confirmation sequence " GR relevant " and GR assignemnt is checked or not, in SPRO > MM> Purchasing --> Confirmations --> Set up confirmation control.

Similar Messages

Rules are not allowed for jobs with set 'archive edited messages only' flag.

Hi,
We are on AEX 7.4 and have enabled user defined search and also setup archiving. Even though the retention period has expired but still the messages are not being
archived.
We see following issues:
1. Unable to setup archiving rule in Runtime Work Bench, we are getting following error:
Rules are not allowed for jobs with set 'archive edited messages only flag.
2. Unable to set the expiration of messages using the following link.Each time we specify the number days it shows the same number of
messages expired.
http://XXXXX:50000/MessagingSystem/job/reorgdb.jsp
3. However if we click on "remove messages" button the messages are getting deleted which tells me that the messages are not matching any
archiving rule hence are being removed.
Any pointers to the above issue are appreciated!!!
Thanks,
Rajeev

Hi,
Please check the [link|http://www.****************/Tutorials/XI/Archiving/Index.htm]
Also check this
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/402fae48-0601-0010-3088-85c46a236f50?quicklink=index&overridelayout=true
http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=147266890
Regards,
Naveen.

Costing run for materials with special procurement key

Hello,
Since moving to ECC6, the costing run for materials with special procurement keys is not pulling the marked price from the materials the special procurement keys point to. Only the released prices are pulled.
Example:
Material A, plant A has a future price (costing 2 tab) of 100 and a current price of 99
Material A, plant B has special procurement key Z1 (costing 1 tab) which pulls the costing from Material A, plant A
In our old system (46c) the costing run for Material A, plant B would pull 100.
In ECC6, the costing run for Material A, plant B pulls 99
Anyone that can push me in the right direction?

Hi,
Based on the info provided thus far, the result that you notice in ECC 6.0 is right as it is picking the current standard price based on your setup.
Now why it is picking the future price in 4.6c, well for that you will have to do a detail check as in which variant is being used etc. I would suggest you to work with your CO personnel on this. Do a costing run for this particular material via CK11n using the variant which you mentioned & see the results.
Or if you can upload the screenshots (picasaweb or some other portal) of the valuation variant you're using in 4.6c, along with Acctng view 1 & 2, costing view 1 & 2 details of the material it would help to have a better understanding.
Regards,
Vivek

"Inbound deliveries for PO reciepts with confirmation control keys"

Hi Gurus,
Can somebody tell me the detailed configuaration steps " Inbound deliveries for PO reciepts with confirmation control keys".
Thanks
Raj

Hi,
Del. type is identified in
OLME-Confirmations-Define Internal Confirmation Categories
Del. item catogery is defined in TCode 0184.
Based on Del. type & item cat. grp in Material master
Goods Recieving point (shipping point) against Plant & SLOC is defined in
Logistics Execution-Shipping-Basic Shipping Functions-Shipping Point and Goods Receiving Point Determination-Assign Goods Receiving Points for Inbound Deliveries

PeopleSoft 8.52 Plug-in Implementation Guide for use with Grid Control

Per the Readme accompanying the download of PeopleSoft 8.52 Plug-in for use with Grid Control (11.1.0.1)-- "For the implementation reference guide, refer to "PeopleSoft Enterprise Environment Management Plug-in 8.52 for Oracle Enterprise Manager Implementation Guide" which you can download from Oracle Technology Network."
I don't seem able to find it.
Can anyone point me in the right direction?
TIA
Jeri

Duh, I was looking on the wrong site.

InvalidKeyException: Could not initialize for signing with the given key

InvalidKeyException: Could not initialize for signing with the given key
What does this caused? And how can I make following code to work? Is it bug, or is it supposed to do so?
X509CertImpl newCert = new X509CertImpl(certInfo);
newCert.sign(caPrivateKey, SIG_ALG_NAME);

Your key is probably using a different algorithm:
Signature signature =
Signature.getInstance( SIGNATURE_ALGORITHM );
PrivateKey privKey =
( PrivateKey ) this.store.getKey( alias, pwd );
Make sure the SIGNATURE_ALGORITHM (SHA1WithRSA, SHA1WithDSA)
matches the algoright of the keystore.
your will see it when casting the private key into a concrete
key instance:
RSAPrivateKey privKey =
( RSAPrivateKey ) this.store.getKey( alias, pwd );

Conf Control Key

Hi Experts
I have a requirement to implement Conf Control key in only one of the Plant.
What are all the factors to be considered before going for it ? What are all the Impacts of it ?

Hi,
The confirmation control key usage is not at the plant level. It is always used if you would like to take an advantageous use of the standard vendor confirmation functionality. As soon as the related setting in configuration (under IMG ---> Material Management --> Purchasing ---> Confirmations ...) is made properly, you can be able to use it. However, you should bear in mind that this vendor confirmation feature is used when you would like to monitor the status of your shipment after PO is sent. This is normally put in use together with expediting feature where SAP will enable you to generate dunning/reminder letters if the vendor fails to either acknowledge receipt of your PO or make on time delivery. In addition, once this feature is utilized, make sure the related confirmation control key shall be maintained in the PO before posting GR.
Cheers,
HT

Keyboard problem with T410 - Control Key

I have a problem with the control keys on the keyboard of T410.
I swapped my X200 keyboard over to T410 to check if it is software or hardware issues. With the X200 keyboard, the 'Ctrl' key is not working. With the T410 keyboard, 'e', 'd', 'c' and 'Ctrl' keys are not working.

Welcome to the forum!
I believe that X200 and T410 keyboards are mapped differently in BIOS.
Can you find another T410/T510 keyboard to test with?
Cheers,
George
In daily use: R60F, R500F, T61, T410
Collecting dust: T60
Enjoying retirement: A31p, T42p,
Non-ThinkPads: Panasonic CF-31 & CF-52, HP 8760W
Starting Thursday, 08/14/2014 I'll be away from the forums until further notice. Please do NOT send private messages since I won't be able to read them. Thank you.

TRAVEL MGMNT -Calculn of Per Diem allowance for trip with Additional Destns

Hello,
I am facing this issue. Please help me.
Details of Trip.
Duration: 2 days exact
Nature: Domestic.
Additonal Destinations: 2
Per diem allowance rate is 50 per day. So it should calculate 100(50 * 2 days). But it calculating 50*4 = 200.
4 line items i.e. calculating per diem for additional destination. I have checked the config but without success.
Pls help.
Regards,
Vijay

Hi,
The system tries to settle per diem allowance for each trip destination.You might have defined per deim allowance for 24 hrs. So it is calculating allowance for 4 days. To get allowance for 2 days, you have to define per deim allowance sclaed by hours.
To configure per deim allowance scaled by hours,
TM>Travel expenses>Trip reimbursement amounts>Reimbursement amounts for meals>Reimbursement amounts for meals/hours>perdeims for meals>Calculation guidelines:define meals per deim scaled by hours.
regards
Vani

CK40N - Update for material with price control 'V'

i Experts,
When im running standard cost estimate in CK40N, say for material types semi finished. The components that is raw materials of the SFG is also updated with the price, meaning for a raw material with price control 'V' has a price of 10, after
releasing the cost estimate for the SFG, when i look into the material master of raw material, the price of 10 is also updated
in the standard price.
I am not sure why this is happening, i believe it should not happen. Because in the valuation variant, if i give the strategy as standard price, this price is easily picked up. And more over with price control 'V', i can change the standard price. Can anybody throw some light on this.
Best regards
gj

Hi Rakesh,
Thanks for the information. But i do agree even during release there is no impact on the inventory. But in my cost variant, say in PPC1, if i give the strategy say 1. standard price 2. moving average price, during cost estimate run, its going to take the standard price for the material irrespective of the price derived automatically for moving average price. For eg in our case for raw material with price control 'V' after sce run if the standard price is 10 and moving average price is 14, as per strategy of PPC1 above its going to take 10 and not 14.
Is there any other way to avoid this. Please correct me if i had went wrong somewhere.
Best regards
gj

BDC program for rebate with table controls

Hi Friends,
Iam Doing bdc program for Rebate(TCODE VBO1) with table controls..
can u give the solutions for table controls...
if anybody having the code..please send me..
Thanks & Advance,
sampath

hi,
check this example it may help you.
REPORT ZSR_BDC_TBCTRL
        NO STANDARD PAGE HEADING LINE-SIZE 255.
TABLES : RF02K,LFA1,LFBK.
DATA : BEGIN OF IT_VEN OCCURS 0,
      LIFNR LIKE RF02K-LIFNR,
      KTOKK LIKE RF02K-KTOKK,
      NAME1 LIKE LFA1-NAME1,
      SORTL LIKE LFA1-SORTL,
      LAND1 LIKE LFA1-LAND1,
      SPRAS LIKE LFA1-SPRAS,
      BANKS(6) TYPE C,
      BANKL(17) TYPE C,
      BANKN(19) TYPE C,
      END OF IT_VEN.
DATA : BEGIN OF BANKS OCCURS 0,
       BANKS LIKE LFBK-BANKS,
       END OF BANKS,
       BEGIN OF BANKL OCCURS 0,
       BANKL LIKE LFBK-BANKL,
       END OF BANKL,
       BEGIN OF BANKN OCCURS 0,
       BANKN LIKE LFBK-BANKN,
       END OF BANKN.
DATA : FLD(20) TYPE C,
       CNT(2) TYPE N.
DATA : BDCTAB LIKE BDCDATA OCCURS 0 WITH HEADER LINE.
INCLUDE BDCRECX1.
START-OF-SELECTION.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
    FILENAME                      = 'Z:\sr.TXT'
   FILETYPE                      = 'ASC'
   HAS_FIELD_SEPARATOR           = 'X'
HEADER_LENGTH                 = 0
READ_BY_LINE                  = 'X'
DAT_MODE                      = ' '
CODEPAGE                      = ' '
IGNORE_CERR                   = ABAP_TRUE
REPLACEMENT                   = '#'
CHECK_BOM                     = ' '
IMPORTING
FILELENGTH                    =
HEADER                        =
TABLES
    DATA_TAB                      = IT_VEN
EXCEPTIONS
FILE_OPEN_ERROR               = 1
FILE_READ_ERROR               = 2
NO_BATCH                      = 3
GUI_REFUSE_FILETRANSFER       = 4
INVALID_TYPE                  = 5
NO_AUTHORITY                  = 6
UNKNOWN_ERROR                 = 7
BAD_DATA_FORMAT               = 8
HEADER_NOT_ALLOWED            = 9
SEPARATOR_NOT_ALLOWED         = 10
HEADER_TOO_LONG               = 11
UNKNOWN_DP_ERROR              = 12
ACCESS_DENIED                 = 13
DP_OUT_OF_MEMORY              = 14
DISK_FULL                     = 15
DP_TIMEOUT                    = 16
OTHERS                        = 17
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
PERFORM OPEN_GROUP.
LOOP AT IT_VEN.
    REFRESH BDCDATA.
    REFRESH : BANKS,BANKL,BANKN..
    SPLIT IT_VEN-BANKS AT ',' INTO TABLE BANKS.
    SPLIT IT_VEN-BANKL AT ',' INTO TABLE BANKL.
    SPLIT IT_VEN-BANKN AT ',' INTO TABLE BANKN.
PERFORM BDC_DYNPRO      USING 'SAPMF02K' '0100'.
PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                              'RF02K-KTOKK'.
PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                              '/00'.
PERFORM BDC_FIELD       USING 'RF02K-LIFNR'
                              IT_VEN-LIFNR.
PERFORM BDC_FIELD       USING 'RF02K-KTOKK'
                              IT_VEN-KTOKK.
PERFORM BDC_DYNPRO      USING 'SAPMF02K' '0110'.
PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                              'LFA1-SPRAS'.
PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                              '/00'.
PERFORM BDC_FIELD       USING 'LFA1-NAME1'
                              IT_VEN-NAME1.
PERFORM BDC_FIELD       USING 'LFA1-SORTL'
                              IT_VEN-SORTL.
PERFORM BDC_FIELD       USING 'LFA1-LAND1'
                              IT_VEN-LAND1.
PERFORM BDC_FIELD       USING 'LFA1-SPRAS'
                              IT_VEN-SPRAS.
PERFORM BDC_DYNPRO      USING 'SAPMF02K' '0120'.
PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                              'LFA1-KUNNR'.
PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                              '/00'.
PERFORM BDC_DYNPRO      USING 'SAPMF02K' '0130'.
PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                              'LFBK-BANKN(02)'.
PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                              '=ENTR'.
*perform bdc_field       using 'LFBK-BANKS(01)'
                             'DE'.
*perform bdc_field       using 'LFBK-BANKS(02)'
                             'DE'.
*perform bdc_field       using 'LFBK-BANKL(01)'
                             '10020030'.
*perform bdc_field       using 'LFBK-BANKL(02)'
                             '67270003'.
*perform bdc_field       using 'LFBK-BANKN(01)'
                             '12345'.
*perform bdc_field       using 'LFBK-BANKN(02)'
                             '66666'.
MOVE 1 TO CNT.
    LOOP AT BANKS.
      CONCATENATE 'LFBK-BANKS(' CNT ') ' INTO FLD.
      PERFORM BDC_FIELD USING FLD BANKS-BANKS.
      CNT = CNT + 1.
    ENDLOOP.
    MOVE 1 TO CNT.
    LOOP AT BANKL.
      CONCATENATE 'LFBK-BANKL(' CNT ') ' INTO FLD.
      PERFORM BDC_FIELD USING FLD BANKL-BANKL.
      CNT = CNT + 1.
    ENDLOOP.
    MOVE 1 TO CNT.
    LOOP AT BANKN.
      CONCATENATE 'LFBK-BANKN(' CNT ') ' INTO FLD.
      PERFORM BDC_FIELD USING FLD BANKN-BANKN.
      CNT = CNT + 1.
    ENDLOOP.
PERFORM BDC_DYNPRO      USING 'SAPMF02K' '0130'.
PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                              'LFBK-BANKS(01)'.
PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                              '=ENTR'.
PERFORM BDC_DYNPRO      USING 'SAPLSPO1' '0300'.
PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                              '=YES'.
PERFORM BDC_TRANSACTION USING 'XK01'.
ENDLOOP.
PERFORM CLOSE_GROUP.&----
*& Report ZSR_BDC_TBCTRL
REPORT ZSR_BDC_TBCTRL
        NO STANDARD PAGE HEADING LINE-SIZE 255.
TABLES : RF02K,LFA1,LFBK.
DATA : BEGIN OF IT_VEN OCCURS 0,
      LIFNR LIKE RF02K-LIFNR,
      KTOKK LIKE RF02K-KTOKK,
      NAME1 LIKE LFA1-NAME1,
      SORTL LIKE LFA1-SORTL,
      LAND1 LIKE LFA1-LAND1,
      SPRAS LIKE LFA1-SPRAS,
      BANKS(6) TYPE C,
      BANKL(17) TYPE C,
      BANKN(19) TYPE C,
      END OF IT_VEN.
DATA : BEGIN OF BANKS OCCURS 0,
       BANKS LIKE LFBK-BANKS,
       END OF BANKS,
       BEGIN OF BANKL OCCURS 0,
       BANKL LIKE LFBK-BANKL,
       END OF BANKL,
       BEGIN OF BANKN OCCURS 0,
       BANKN LIKE LFBK-BANKN,
       END OF BANKN.
DATA : FLD(20) TYPE C,
       CNT(2) TYPE N.
DATA : BDCTAB LIKE BDCDATA OCCURS 0 WITH HEADER LINE.
INCLUDE BDCRECX1.
START-OF-SELECTION.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
    FILENAME                      = 'Z:\sr.TXT'
   FILETYPE                      = 'ASC'
   HAS_FIELD_SEPARATOR           = 'X'
HEADER_LENGTH                 = 0
READ_BY_LINE                  = 'X'
DAT_MODE                      = ' '
CODEPAGE                      = ' '
IGNORE_CERR                   = ABAP_TRUE
REPLACEMENT                   = '#'
CHECK_BOM                     = ' '
IMPORTING
FILELENGTH                    =
HEADER                        =
TABLES
    DATA_TAB                      = IT_VEN
EXCEPTIONS
FILE_OPEN_ERROR               = 1
FILE_READ_ERROR               = 2
NO_BATCH                      = 3
GUI_REFUSE_FILETRANSFER       = 4
INVALID_TYPE                  = 5
NO_AUTHORITY                  = 6
UNKNOWN_ERROR                 = 7
BAD_DATA_FORMAT               = 8
HEADER_NOT_ALLOWED            = 9
SEPARATOR_NOT_ALLOWED         = 10
HEADER_TOO_LONG               = 11
UNKNOWN_DP_ERROR              = 12
ACCESS_DENIED                 = 13
DP_OUT_OF_MEMORY              = 14
DISK_FULL                     = 15
DP_TIMEOUT                    = 16
OTHERS                        = 17
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
PERFORM OPEN_GROUP.
LOOP AT IT_VEN.
    REFRESH BDCDATA.
    REFRESH : BANKS,BANKL,BANKN..
    SPLIT IT_VEN-BANKS AT ',' INTO TABLE BANKS.
    SPLIT IT_VEN-BANKL AT ',' INTO TABLE BANKL.
    SPLIT IT_VEN-BANKN AT ',' INTO TABLE BANKN.
PERFORM BDC_DYNPRO      USING 'SAPMF02K' '0100'.
PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                              'RF02K-KTOKK'.
PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                              '/00'.
PERFORM BDC_FIELD       USING 'RF02K-LIFNR'
                              IT_VEN-LIFNR.
PERFORM BDC_FIELD       USING 'RF02K-KTOKK'
                              IT_VEN-KTOKK.
PERFORM BDC_DYNPRO      USING 'SAPMF02K' '0110'.
PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                              'LFA1-SPRAS'.
PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                              '/00'.
PERFORM BDC_FIELD       USING 'LFA1-NAME1'
                              IT_VEN-NAME1.
PERFORM BDC_FIELD       USING 'LFA1-SORTL'
                              IT_VEN-SORTL.
PERFORM BDC_FIELD       USING 'LFA1-LAND1'
                              IT_VEN-LAND1.
PERFORM BDC_FIELD       USING 'LFA1-SPRAS'
                              IT_VEN-SPRAS.
PERFORM BDC_DYNPRO      USING 'SAPMF02K' '0120'.
PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                              'LFA1-KUNNR'.
PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                              '/00'.
PERFORM BDC_DYNPRO      USING 'SAPMF02K' '0130'.
PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                              'LFBK-BANKN(02)'.
PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                              '=ENTR'.
*perform bdc_field       using 'LFBK-BANKS(01)'
                             'DE'.
*perform bdc_field       using 'LFBK-BANKS(02)'
                             'DE'.
*perform bdc_field       using 'LFBK-BANKL(01)'
                             '10020030'.
*perform bdc_field       using 'LFBK-BANKL(02)'
                             '67270003'.
*perform bdc_field       using 'LFBK-BANKN(01)'
                             '12345'.
*perform bdc_field       using 'LFBK-BANKN(02)'
                             '66666'.
MOVE 1 TO CNT.
    LOOP AT BANKS.
      CONCATENATE 'LFBK-BANKS(' CNT ') ' INTO FLD.
      PERFORM BDC_FIELD USING FLD BANKS-BANKS.
      CNT = CNT + 1.
    ENDLOOP.
    MOVE 1 TO CNT.
    LOOP AT BANKL.
      CONCATENATE 'LFBK-BANKL(' CNT ') ' INTO FLD.
      PERFORM BDC_FIELD USING FLD BANKL-BANKL.
      CNT = CNT + 1.
    ENDLOOP.
    MOVE 1 TO CNT.
    LOOP AT BANKN.
      CONCATENATE 'LFBK-BANKN(' CNT ') ' INTO FLD.
      PERFORM BDC_FIELD USING FLD BANKN-BANKN.
      CNT = CNT + 1.
    ENDLOOP.
PERFORM BDC_DYNPRO      USING 'SAPMF02K' '0130'.
PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                              'LFBK-BANKS(01)'.
PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                              '=ENTR'.
PERFORM BDC_DYNPRO      USING 'SAPLSPO1' '0300'.
PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                              '=YES'.
PERFORM BDC_TRANSACTION USING 'XK01'.
ENDLOOP.
PERFORM CLOSE_GROUP.

Update PO with Confirmation Control Key,Acknowledged Delivery Date.

Hi Experts,
I have a requirement that through a Excel file I have to update a Existing PO with the three fields,
1.Confirmation Control Key
2.Acknowledged Delivery Date.
3.Acknowledged Modified Delivery Date.
If there will be differ in values in any of the field in the existing PO and the incoming excel file then we need to update the
fields in the PO.
So is there any BAPI or FM to update the field value?
I tried with BAPI_PO_CHANGE it is not working.
In excel we have only five fields.
1.PO number
2.Item
3.Confirmation Control Key
4.Acknowledged Delivery Date.
5.Acknowledged Modified Delivery Date
Please help.
Regards,
Umesh

you can use BAPI_PO_CHANGE itself, but you need to get the details of the current PO before passing the details to BAPI_PO_CHANGE
you can use BAPI_PO_GETDETAIL1 by passing ( PURCHASEORDER = <..Your Purchase order Number..> ) and after that you willl
get all the details of the PO, just change the required data's and pass it to the BAPI_PO_CHANGE. It will be easier.
after you receive all the data,
pass the corresponding data from BAPI_PO_GETDETAIL1
to BAPI_PO_CHANGE.
1.PO number                    -     PURCHASEORDER (importing)
2.Item                         -     POITEM (Tables )
3.Confirmation Control Key          -     POCONFIRMATION (Tables)
4.Acknowledged Delivery Date.
5.Acknowledged Modified Delivery Date
I think for 4,5 fields are also in POCONFIRMATION table itself (not sure)

Return key broken, only works with holding control key

I think my young daughter did something on accident while using the computer.
The return key only works now while holding down the control key. It will not work as it normally should. I do alot of word processing on my computer and this is an big hassle now.
Please help. This is a serious pain in my.........
thanks - sam

a brody, I did already try my older mac keyboard and it has the same problem. Here is a couple more pieces of info that may help.
When this started, my daughter was playing the apple Chess game. With the voice. This problem started after that. And, with my current problem, sometimes the voice comes on and will read me a folder name, or read me my email subject.
Today, the return key started working for a few hours, but then stopped again.
This is weird and i am clueless. Anymore thoughts??

Time-split not allowed for routines with return tables

I've had this issue a couple of times. It was usually a date field was incorrect. I have not made any changes concerning update rules. Any ideas?
Thanks everyone!
-Ryan.

Hi,
Normally, the date format is common accross R/3 and BW so as long as it is
stright forward date value then you won't get any errors.
else, if you are using date field and trying to assign to a fisacl period or Fiscal year
then you would have to sub string the date and manipulate accordinly..
like ex: BUDAT+(6) : 200702
BUDAT+(4): 2007
BUDAT+4(2) : 02
Hope this helps..
assign points if useful..
Cheers,
Pattan.

Production costs for material with price control V

Dear all,
Can anyone pls tell me, how will the costing occur for a material produced in-house and having price control 'V' ? I am not able to see the target costs.
Also kindly tell me the settings to be done in CO, like target cost version, valuation variant, costing variant, etc.
Thank you,
Shrenik

Rather than giving my own versions I have compiled here SAP inputs. Pl let me know if you require any clarifications:
Costing variant has the following components:
<b>Define Costing Types
Define Valuation Variants
Define Date Control
Define Quantity Structure Control
Define Transfer Strategy
Define Reference Variants</b>
<u>Costing type:</u>
In the costing type, you define the purpose of a material cost estimate by specifying, for example, which field in the material master record the costing results can be transferred to:
Update Cost Estimate
Standard price Standard cost estimate (01)
Tax-based price Inventory cost estimate
Commercial price Inventory cost estimate
Price other than std price Modified standard cost estimate or
current cost estimate
No update Any cost estimate
Define Valuation Variants:
Define Valuation Variants
Here you create a valuation variant containing the parameters required for valuation of a cost estimate.
You also specify which costing sheet should be used to calculate overhead.
Valuation Strategies
Material valuation
Here you define the sequence in which the system searches for prices from the accounting view or costing view of the material master record to valuate materials. You can also access prices from purchasing info records and condition types.
For material cost estimates, you also specify whether additive costs can be added to the selected price.
With configurable/configured material components and with procurement alternatives, the sequence defined here is ignored if the strategy "price from purchasing info record" was selected, in which case that strategy is always executed first. For more information, refer to the SAP Library in the component Product Cost Planning under Raw Material Costing or Mixed Costing.
Activity Types / Processes
Here you define the sequence in which the system searches for prices in activity type planning or actual activity price calculation in Cost Center Accounting or Activity-Based Costing to valuate the utilized activity types and business processes.
You also specify which plan/actual version is used.
Subcontracting
Here you define the sequence in which the system searches for prices in the purchasing info record. In purchasing, quota arrangements are used to create a mixed price for materials that are manufactured with external vendors with parts provided by the customer. You can specify whether the quota of the individual vendors that are entered in the source list for the material to be processed should be determined through the planned quota arrangement or the actual quota arrangement.
External processing
Here you define the sequence in which the system searches for prices in the purchasing info record or routing operation for valuation of the external activities.
Strategy Sequence
You define the individual valuation methods for the valuation variant as strategy sequences. For the valuation of the material components you define a strategy sequence that reads the fields of the material master record in a particular sequence such as:
1. Planned price 1
2. Standard price
3. Moving price
The first price that is not zero is used to valuate the material component.
Target versions:
Target cost versions are used in the following ways:
In variance calculation:
To control which variance (total variance, production variances or planning variance) is calculated
To valuate unplanned scrap( scrap variance)
Unplanned scrap is valuated in the period-end closing activities when the variances are calculated. You can specify in a valuation variant for WIP and scrap which cost estimate you want to use to calculate the target costs for the valuation of unplanned scrap. You assign the valuation variant to target cost version 0 if you want to include it in the valuation of scrap.
When you are using a cost object hierarchy with active distribution, you use the target cost version to control which cost estimate the system uses to calculate the target costs, which are used as the basis for determining equivalences for actual cost distribution.
The actual costs collected at the level of the hierarchy are distributed across the orders in accordance with these equivalences. This distribution is proportional to the target costs for the cost element under which the actual costs are written. Actual costs for material costs are distributed in proportion to the target costs for the origin group, such as for the material, if you have entered an origin group in the costing view of the material master record and have set the indicator Material origin, for example.
If no target costs were calculated under this cost element, enter a cost element group in the target cost version. The actual costs are distributed in proportion to the target costs for this cost element group. This cost element group should be complete. If costs were updated under a cost element that is not in this cost element group, no distribution is possible.
You can calculate equivalences on the basis of SAP standard target cost versions 0, 1 and 3.
The standard system supplies the following target cost versions:
Target cost version 0 ( total variance)
The amount of the total variance generates a posting in Financial Accounting during settlement.
For this version, select actual costs as the control costs and standard cost estimate as the target costs.
Target cost version 1 ( production variance)
For this version you choose actual costs as the control costs and planned costs as the target costs.
Target cost version 2( planning variance)
With target cost version 2, the costs from the preliminary order cost estimate are interpreted as control costs.
For this version, select planned costs as the control costs and current cost estimate as the target costs. You cannot calculate planning variances for the product cost collector.
Target cost version 3 (production variance of the period)
You compare the planned costs of the period calculated on the basis of an alternative material cost estimate (such as a modified standard cost estimate) with the actual costs of the period on the basis of the yield delivered to stock in the period.
The base quantity for variance calculation is the yield.
For this version, you choose the actual costs as the control costs and the alternative material cost estimate as the target costs. To determine the alternative material cost estimate, enter a costing variant and choose a costing version.
The target cost version specifies which data is to be compared. The target cost version also specifies which variance variant is used and therefore which variance catagories are calculated. You can define a different target cost version for each controlling area

GR via MIGO allowed for POs with conf control key

Similar Messages

Maybe you are looking for