Unable to determine a calculation schema

Hi ALL,
I am getting warning while creating RFQ:-
Unable to determine a calculation schema
Message no. 06248
please tell me why this warning massage is coming,and how to correct this so that it wont show next time while i do business to same vendor.
With Regards,
Siddharth Shanker

Hi,
In the Materials Management area, a calculation schema - a framework of steps used to calculate costs, prices and taxes etc.
pls chk whether calculation schema is defined thru following path
IMG>>Materials Management >>>Purchasing >>>Conditions>>Define Price Determination Process>>Define Calculation Schema
Br,
Tushar Patankar

Similar Messages

Message 02648: "Unable to determine a calculation squema"

Hello everyone,
Does anyone of you heard about Message 02648: "Unable to determine a calculation squema"?
It appears when creating a PO referred to a Preq via TX-ME21, but it does not appear when doing it via TX-ME57.
I would reallly appreciate any info relating this issue.
Thank you very much in advanced,
Víctor Liedo

the message number is 06 248.
a calculation schema is assigned to a schema group, the schema group is entered in the vendor master.
alternative a calculation schema can be assigned to a purchasing org.
Check first the vendor master in purchasing data view whether the schema group was entered properly.
If that is okay, then check in customizing whether the assignments have been made properly.

Issue in Calculation schema determination for Scheduling Agreements

Dear All,
I am facing an issue in Calculation schema determination for Scheduling Agreements. The issue is -
"Appropriate calculation schema is not being determined when a scheduling agreement is being created"
The required settings which have been maintained are - The Calculation Schema (ZEIC31) has been created, Vendor Schema group has been created, Purchasing Organisation Schema group has been created, They both have been assigned to the Calculation schema in Schema determination, The Vendor Schema group has been assigned to the Vendor Master Record in master data creation.
When I am creating the scheduling agreement, the system is by default choosing the calculation schema - RM0002. Thus I am not able to put the manual condition types which have been assigned in the calculation schema - ZEIC31.
1> On what logic is the system picking that calculation schema?
2> What settings can I do to make it pick that calculation schema only which has been assigned with POrg Sch Gp and Ve Sch Gp?
Regards,
Sudhanshu

1> On what logic is the system picking that calculation schema?
As per "Define Schema Determination" in spro Purchasing document should pick the Pricing Procedure .
After creation of scheduling agreement have chacked your values in Scheduling agreement (Purchase ORG ,Schema grp in Vendor)
2> What settings can I do to make it pick that calculation schema only which has been assigned with POrg Sch Gp and Ve Sch Gp?
Check in Vendor mater is there any Plant specific Purcahsing data maintained.If it is plant specific Check purchasing data for that Plant.

User Exit for PO Calculation Schema Determination by PO Document Type

Hello,
Due to complex pricing requirements for both standard inbound purchase orders and return to vendor purchase orders, we need two separate calculation schemas to be applicable to each vendor.
I have configured the primary calculation schema (ZM1000) which is correctly calculated on our standard purchase orders. Through ENHANCEMENT-POINT mepo_header_fill_neu_01 SPOTS es_saplmepo (program SAPLMEPO) we have implemented code to change the calculation schema to the return schema (ZM1002) if the document type is one of our return purchase order types.
ENHANCEMENT 1 ZMEEI_PO_PRICE_SCHEMA_DETM. "active version
IF fekko-bsart eq 'ZR1' or fekko-bsart eq 'ZR2' or fekko-bsart eq 'ZR3' or fekko-bsart eq 'ZR4' .
fekko-kalsm = 'ZM1002'.
ENDIF.
ENDENHANCEMENT.
We are facing an issue where once the data is correctly entered into the return PO and the pricing has been determined there are errors. The following is observed in the pricing analysis:
1) The correct calculation schema is determined (ZM1002).
2) Pricing conditions which have a condition record under the main calculation schema (ZM1000), but which do not exist in the return one (ZM1002) still appear in the pricing. This is an issue.
3) Price conditions which have a condition record under the new schema (ZM1002), and which should appear, receive the message "Condition record exists, but has not been set". This is an issue.
When the pricing is re-determined manually at the line item level, it recalculates correctly and issues 2 and 3 above are adjusted accordingly.
Question:
Is there something missing in our code above which is cause these issues or is there a better user exit we should be using to address this requirement?
Thanks in advance!

Melih
What we ended up doing was using ENHANCEMENT-POINT item_process_main_01 SPOTS es_saplmepo (program SAPLMEPO) to re-price the line items automatically when processing. This solved our issue.
IF EKKO-BSART = 'ZR1' or EKKO-BSART = 'ZR2' or EKKO-BSART = 'ZR3' or
EKKO-BSART = 'ZR4'.
lf_ext_calctype = 'C'.
ENDIF.

The directory service is missing mandatory configuration information, and is unable to determine the ownership of floating single-master operation roles.

We are in the process of removing a child domain from the forest and are down to two DCs. These are both Server 2008r2 sp1 servers, one physical and virtual (PDC). When I try to remove a DC (not the PDC emulator) I get the following error:
The operation failed because:
Active Directory Domain Services could not transfer the remaining data in directory partition DC=DomainDnsZones,DC=mydomain,DC=local to
Active Directory Domain Controller \\V-Svr03.mydomain.local.
The directory service is missing mandatory configuration information, and is unable to determine the ownership of floating single-master operation roles."
I have checked replication with repadmin /showrepl and all connections were successful. The dcdiag /test:kccEvent test on all servers passed.
Most DCdiag tests are successful. The only failure is on NCSecDesc when running dcdiag /test:NCSecDesc
   Testing server: Default-First-Site\DC1-DEV-OFC
      Starting test: NCSecDesc
         Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
            Replicating Directory Changes In Filtered Set
         access rights for the naming context:
         DC=ForestDnsZones,DC=hookemup,DC=local
         ......................... DC1-DEV-OFC failed test NCSecDesc
In researching this I find "If you do not plan to add an RODC to the forest, you can disregard this error."
We have not successfully run ADprep /rodcPrep nor do we plan on having any Read-Only DCs, so I think we can ignor this error. We did try running ADprep /rodcPrep but got an LDAP error which I can duplicate if this is important.
Schema and Naming FSMOs are on a DC higher in the forest. RID, PDC, and Infrastructure FSMOs for the child domain are on the Virtual server (PDC).
Any guidance on where to go from here would be greatly appreciated as I have no more hair on my head to pull.

Ok... I ran repadmin /showreps /v again and it shows no errors
C:\>repadmin /showreps /v
Default-First-Site\DC1-DEV-OFC
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: b294c59f-8b46-4133-89c5-0f30bfd49607
DSA invocationID: 1054285d-cffe-42b4-8074-e2d44adbb151
==== INBOUND NEIGHBORS ======================================
CN=Configuration,DC=mydomain,DC=local
    Default-First-Site\HESTIA via RPC
        DSA object GUID: b464fde9-29d7-4490-9582-fe9270050d50
        Address: b464fde9-29d7-4490-9582-fe9270050d50._msdcs.mydomain.local
        DSA invocationID: afea3845-9fa8-40a6-a477-84348a206348
        SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
        USNs: 16381490/OU, 16381490/PU
        Last attempt @ 2012-10-29 13:52:39 was successful.
    Default-First-Site\V-SVR03 via RPC
        DSA object GUID: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8
        Address: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8._msdcs.mydomain.local
        DSA invocationID: 45de2c10-ec8b-443d-a645-db4e0a352a23
        SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
        USNs: 114817/OU, 114817/PU
        Last attempt @ 2012-10-29 13:52:39 was successful.
    Default-First-Site\V-SVR01 via RPC
        DSA object GUID: e2f794eb-9658-4bad-b695-3d8c08f46371
        Address: e2f794eb-9658-4bad-b695-3d8c08f46371._msdcs.mydomain.local
        DSA invocationID: 07bb0fe9-bca9-46d1-92ce-308d36da478d
        SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
        USNs: 66047/OU, 66047/PU
        Last attempt @ 2012-10-29 13:52:39 was successful.
    Default-First-Site\ATHENA via RPC
        DSA object GUID: cb00a5b0-6dea-473c-bb42-19356dd9ed36
        Address: cb00a5b0-6dea-473c-bb42-19356dd9ed36._msdcs.mydomain.local
        DSA invocationID: 57313a9c-46a2-4b94-87cc-b3f91d54faed
        SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
        USNs: 8098197/OU, 8098197/PU
        Last attempt @ 2012-10-29 13:52:39 was successful.
CN=Schema,CN=Configuration,DC=mydomain,DC=local
    Default-First-Site\ATHENA via RPC
        DSA object GUID: cb00a5b0-6dea-473c-bb42-19356dd9ed36
        Address: cb00a5b0-6dea-473c-bb42-19356dd9ed36._msdcs.mydomain.local
        DSA invocationID: 57313a9c-46a2-4b94-87cc-b3f91d54faed
        SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
        USNs: 8097482/OU, 8097482/PU
        Last attempt @ 2012-10-29 13:52:39 was successful.
    Default-First-Site\V-SVR01 via RPC
        DSA object GUID: e2f794eb-9658-4bad-b695-3d8c08f46371
        Address: e2f794eb-9658-4bad-b695-3d8c08f46371._msdcs.mydomain.local
        DSA invocationID: 07bb0fe9-bca9-46d1-92ce-308d36da478d
        SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
        USNs: 65239/OU, 65239/PU
        Last attempt @ 2012-10-29 13:52:39 was successful.
    Default-First-Site\V-SVR03 via RPC
        DSA object GUID: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8
        Address: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8._msdcs.mydomain.local
        DSA invocationID: 45de2c10-ec8b-443d-a645-db4e0a352a23
        SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
        USNs: 114149/OU, 114149/PU
        Last attempt @ 2012-10-29 13:52:39 was successful.
    Default-First-Site\HESTIA via RPC
        DSA object GUID: b464fde9-29d7-4490-9582-fe9270050d50
        Address: b464fde9-29d7-4490-9582-fe9270050d50._msdcs.mydomain.local
        DSA invocationID: afea3845-9fa8-40a6-a477-84348a206348
        SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
        USNs: 16381373/OU, 16381373/PU
        Last attempt @ 2012-10-29 13:52:39 was successful.
DC=ForestDnsZones,DC=mydomain,DC=local
    Default-First-Site\V-SVR01 via RPC
        DSA object GUID: e2f794eb-9658-4bad-b695-3d8c08f46371
        Address: e2f794eb-9658-4bad-b695-3d8c08f46371._msdcs.mydomain.local
        DSA invocationID: 07bb0fe9-bca9-46d1-92ce-308d36da478d
        SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
        USNs: 66295/OU, 66295/PU
        Last attempt @ 2012-10-29 13:57:48 was successful.
    Default-First-Site\ATHENA via RPC
        DSA object GUID: cb00a5b0-6dea-473c-bb42-19356dd9ed36
        Address: cb00a5b0-6dea-473c-bb42-19356dd9ed36._msdcs.mydomain.local
        DSA invocationID: 57313a9c-46a2-4b94-87cc-b3f91d54faed
        SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
        USNs: 8098367/OU, 8098367/PU
        Last attempt @ 2012-10-29 13:58:13 was successful.
    Default-First-Site\V-SVR03 via RPC
        DSA object GUID: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8
        Address: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8._msdcs.mydomain.local
        DSA invocationID: 45de2c10-ec8b-443d-a645-db4e0a352a23
        SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
        USNs: 115032/OU, 115032/PU
        Last attempt @ 2012-10-29 13:58:25 was successful.
    Default-First-Site\HESTIA via RPC
        DSA object GUID: b464fde9-29d7-4490-9582-fe9270050d50
        Address: b464fde9-29d7-4490-9582-fe9270050d50._msdcs.mydomain.local
        DSA invocationID: afea3845-9fa8-40a6-a477-84348a206348
        SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
        USNs: 16381653/OU, 16381653/PU
        Last attempt @ 2012-10-29 13:58:34 was successful.
DC=mySUBdomain,DC=local
    Default-First-Site\V-SVR03 via RPC
        DSA object GUID: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8
        Address: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8._msdcs.mydomain.local
        DSA invocationID: 45de2c10-ec8b-443d-a645-db4e0a352a23
        SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
        USNs: 114871/OU, 114871/PU
        Last attempt @ 2012-10-29 13:54:02 was successful.
DC=DomainDnsZones,DC=mySUBdomain,DC=local
    Default-First-Site\V-SVR03 via RPC
        DSA object GUID: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8
        Address: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8._msdcs.mydomain.local
        DSA invocationID: 45de2c10-ec8b-443d-a645-db4e0a352a23
        SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
        USNs: 114017/OU, 114017/PU
        Last attempt @ 2012-10-29 13:52:39 was successful.
DC=mydomain,DC=local
    Default-First-Site\V-SVR03 via RPC
        DSA object GUID: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8
        Address: 53018cc4-b8c9-48ce-9a54-1b987e7b08c8._msdcs.mydomain.local
        DSA invocationID: 45de2c10-ec8b-443d-a645-db4e0a352a23
        SYNC_ON_STARTUP DO_SCHEDULED_SYNCS
        USNs: 114017/OU, 114017/PU
        Last attempt @ 2012-10-29 13:52:39 was successful.
    Default-First-Site\HESTIA via RPC
        DSA object GUID: b464fde9-29d7-4490-9582-fe9270050d50
        Address: b464fde9-29d7-4490-9582-fe9270050d50._msdcs.mydomain.local
        DSA invocationID: afea3845-9fa8-40a6-a477-84348a206348
        SYNC_ON_STARTUP DO_SCHEDULED_SYNCS
        USNs: 16381614/OU, 16381614/PU
        Last attempt @ 2012-10-29 13:56:52 was successful.
    Default-First-Site\V-SVR01 via RPC
        DSA object GUID: e2f794eb-9658-4bad-b695-3d8c08f46371
        Address: e2f794eb-9658-4bad-b695-3d8c08f46371._msdcs.mydomain.local
        DSA invocationID: 07bb0fe9-bca9-46d1-92ce-308d36da478d
        SYNC_ON_STARTUP DO_SCHEDULED_SYNCS
        USNs: 66325/OU, 66325/PU
        Last attempt @ 2012-10-29 13:58:34 was successful.
    Default-First-Site\ATHENA via RPC
        DSA object GUID: cb00a5b0-6dea-473c-bb42-19356dd9ed36
        Address: cb00a5b0-6dea-473c-bb42-19356dd9ed36._msdcs.mydomain.local
        DSA invocationID: 57313a9c-46a2-4b94-87cc-b3f91d54faed
        SYNC_ON_STARTUP DO_SCHEDULED_SYNCS
        USNs: 8098385/OU, 8098385/PU
        Last attempt @ 2012-10-29 13:58:38 was successful.

PRICING PROCEDURE-CALCULATION SCHEMA

Dear All,
There are some queries regarding pricing procedure calculation schema.Please help me out:
1) What is the use of the "Requirement" column in calculation schema in real time scenario?
2) What is meant by "Alternative calculation type" and "Alternative base value" column?What is its use in real time scenario?
3) In the Print column if we place "X",it says "Printing at item level (previous procedure)".What does this actually means?
4) What is the use of "Accurals" and what effect does it have in the pricing procedure and pricing calculation?
For all the above queries some real time scenario example willbe highly appreciable.
Regards,
Indranil

1) What is the use of the "Requirement" column in calculation schema in real time scenario?
Requirement
Use
    If the requirement is fulfilled (SY-SUBRC = 0), then output
    determination also takes into consideration output type or the access
    sequence, for which the requirement has been specified.
Examples
    A possible requirement would be, for example, that a difference shoul
    be made between document currency and local currency .
Definition
     Number of a subroutine (= form routine), that checks a requirement at a
     specific time.
Use
     The standard SAP system contains some standard routines for checking
     requirements when copying. You can also define your own routines
     according to the needs of your company.
Example
     If you copy a quotation to a sales order, the system can check every
     quotation item to ensure that the customer had not rejected them for any
     reason.
2) What is meant by "Alternative calculation type" and "Alternative base value" column?What is its use in real time scenario?
If you are using any Formula to Derive the Condition Type then you can use Alternative formula to the formula in the standard system that
determines a condition.
Alternative formula for condition base value
     Formula for determining the condition basis as an alternative to t
     standard.
Example
     An absolute header discount is, for example, distributed in the st
     system according to the cumulative value of the items.
     If the system, however, distributes the absolute header discount
     according to volume, a header discount of $30 results in the follo
     discounts:
     Item       Value Volume              Discount
                                  Stand. disc.   Volume disc.
       1        $1000 2 cbm         $20             $10
       2        $500   4 cbm         $10             $20
3) In the Print column if we place "X",it says "Printing at item level (previous procedure)".What does this actually means?
If you Put 'X" , it will be shown in the Print Output..
Print ID for condition lines
     Controls issue of condition lines when printing documents such as order
     confirmations or invoices.
Use
     In releases previous to 4.0, the following print indicators are
     available :
     o   ' ' : Condition line is not printed
     o   'X' : Condition line is printed at item level
     o   'S' : Condition line is printed in totals block
     The following standard logic is set out for these printing indicators:

Accounting Key & Accruals Key in Calculation Schema (Pricing Procedure)

Hi Freinds,
               I have a query regarding use of Accounting Key & accruals key in the Calculation Schema (Pricing Procedure).
What is the significance of Accounting key & accruals key in the calcuation schema? Which Accounting & Accruals keys have to be used for Gross price,Discount,Freight, tax etc in the Calculation schema? Please post your precious threads.
Thanks & Regards
Saeed Arif

hi
AcyKy - Account Key/ Accrls - Accruals:
for SD module
u2022     The values of the Sales Revenues, Sales Deductions, Freight Revenues, Tax Revenues, and Rebate Accruals etc. are going to be posted in the respective G/L accounts in Fi Module.
u2022     In order to do this we assign account keys/ accruals to the different condition types based on their classification. The classification shown below.
o     ERB Rebate sales deduct.
o     ERF Freight revenue
o     ERL Revenue
o     ERS Sales deductions
o     ERU Rebate accruals
u2022     For Ex.,
o     For all Price condition types like PR00 etc. we assign ERL - Revenue.
o     For all Discount condition types like K004, K005 etc. we assign ERS - Sales Deductions.
o     For all Freight condition types KF00 etc. we assign ERF - Freight Revenues.
o     For all Rebates condition types BO01 to BO05 we assign in Account key ERB - Rebates Sales deductions and for Accruals ERU - Rebate Accruals.
u2022     This account keys and accruals are in turn assigned to respective G/L accounts. So the system posts respective values in respective G/L accounts in Fi-Co Module.
u2022     This also one of the areas of SD - Fi Integration. SD consultants assign the account keys and Fi Consultants assign the respective G/L accounts in T.Code:VKOA.
Similarly for MM Module
Account keys are EIN, FR1, FR2, FR3, FRE, etc...
And in OBYC, we do necessary account determination for the same.
For e.g. Freight Posting in GR
Condition type FRA1, Accrual FR1 and in OBYC, assign Freight Clearing A/c to FR1
During GR;
Stock Account - Dr - 110 INR
GR/IR Clearing A/c - Cr - 100 INR
Freight Clearing A/c - Cr - 10 INR
transaction event key is the Key that identifies different types of G/L account.
The account key enables the system to post amounts to certain types of
revenue account. For example, the system can post freight charges
(generated by the freight pricing condition) to the relevant freight
revenue account.
use
To enable the system to find the relevant account for provisions (for
accrued delivery costs or miscellaneous provisions, for example), you
must assign a transaction/event (internal processing) key to each
condition type that is relevant to provisions in the step Define
Calculation Schema.
if u search on SDN or GOOGLE u will get many threads for this
hope it helps
regards
kunal

Calculation Schema on Quotations...

Hi people, ... Question .. , What is the Conditions Calculation Schema used by default when creating a Quotation ? does it uses the Schema related to the standar purchase order ? thanks !

Hi,
These are the standard pricing schemas used in standard SAP.
1) RM0000 and RM1000
For POs, quotations, and scheduling agreements
2) RM0001 and RM1001 for Contracts
3) RM0002 and RM1002 for purchase inforecords
4) RM2000 for stock transport orders and stock transport scheduling agreements
5) RMMP00 for determining the market price which can be entered for each material
Thanks & egards
Anilkumar Dalai

Unable to determine XI party

Hi,
I'm still trying to implement an IDoc to RosettaNet scenario. It seems to work fine until the last step, the sending of the PIP message. In Message Monitoring I get the following error.
Delivering to channel: PIP3B2_V0100_Shipper_Send_AdvanceShipmentNotification
Error Unable to determine XI party '. ' party not configured for party schema DUNS, party agency 016
Error occurred in CPA Facade processing. - Could not find party configuration for Party\=;PartySchema\=DUNS;PartyAgency\=016. - Party found to be null or empty : Could not find party configuration for Party\=;PartySchema\=DUNS;PartyAgency\=016.
The communication channel (type rnif adapter, receiver) belongs to party "TestParty" which has a duns specified. But it seems the system is looking for another party or duns? I have no idea where. It also doesn't make any difference whether I fill in something in tab identifiers of the communication channel or not.
I'll reward points for any helpful answer.
Thanks
Michael

Hi
Refer these blogs
'Close Encounters' with the Rosettanet STK
About Electronic Documents, Business Documents and Messages
SAP Launches Inititative for Industry Content
Service-enabling RosettaNet business processes
regards,
surya

Error in invoice calculation scheme

Hi dears
I have two calculation schemes ZXXX3 and ZXXX31. The second one was created as a copy of ZXXX3, nothing was changed in it.
I assign the new scheme ZXXX31 to my sales area, create sales order and then create invoice via vf01 for this order without problem.
Then I assign the old scheme ZXXX3 to the same sales area instead ZXXX31, create sales order and try to create an invoice. But I can't save it because is shows me an error "interface RW: document data header are inconsistent for updating"
ECC6.0 system
I have equal sales area, customer, material, data and so on. I have difference only in scheme name. The condition exclusion rules are the same for both schemes.

Hi, Phanikumar
I check these schemes in the test system, there fore I can take the same customer / material / quantity / organization data and so on. The pricing procedure is the same in sales order and in invoice.
The invoice is hitting RW because the accounting document is created with reference to invoice, e.g.
Account determination is definited in calculation scheme by accounting key ERL:
The condintions ZPR1 and ZR02 are in different exclusion groups
and these excluding groups are assugned to both calculation schemes.
I've found that if I delete ZR02 condition from ZXXX3 cheme it begins to work. But ZXXX31 works with this condition properly. The scemes were created as copy of each other.

[SOLVED] Unable to determine major/minor number of root device - USB

I installed Arch on a USB harddrive of mine from within VirtualBox with the intention of running the installation (via the drive) on a laptop in my house. I passed through the drive through by creating a special vmdk (here - it's for "expert users only". ) and installed Arch on it by booting off the Arch 2011.08.19 iso and following the instructions. I do recall the installer complaining because /sbin/mkinitcpio was missing, so I copied over the one from the host (which is also an up-to-date Arch system). After that, everything worked and I was able to boot the drive within virtualbox.
Then I went and plugged it in to another laptop in the house and, surprisingly (for me at least), it got past GRUB. My joy was short-lived, because it failed just a bit later:
:: Running Hook [udev]
:: Triggering uevents...done.
ERROR: Unable to determine major/minor number of root device 'Waiting 10 seconds
for device /dev/disk/by-uuid/[the uuid] ...
/dev/disk/by-uuid/(the uuid)'.
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
sh: can't access tty: job control turned off
[ramfs /]#
So I googled around for a while and plugged it back in to my computer, booted it up in virtualbox, and added "usb" to the HOOKS array right after udev in /etc/mkinitcpio.conf. Then I rebuilt the initramfs:
# mkinitcpio -p linux
So I plugged it back into the laptop, booted it, and got the same error.
Later, in an attempt to isolate the problem, I removed "sata" from HOOKS, ran the same mkinitcpio command again, and rebooted the VM. I got what looked like the same error as the one above. yay. So I guess the usb hook isn't being loaded or something like that. (I've since added the "sata" hook back and rebuilt the initramfs so I can mess around in the VM )
I've tried removing autodetect from HOOKS (saw that in some threads) and trying different USB ports on the laptop, but nothing seems to be working. I also checked to see if virtualbox was providing a bogus uuid or something, but the one it's specifying seems to be correct - I looked in my computer's /dev/disk/by-uuid and it matched.
Info on the drive (first partition is /boot, second is swap (derp!), third is /, and fourth is /home):
# sudo fdisk -l /dev/sdg
Disk /dev/sdg: 500.1 GB, 500107861504 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773167 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00016b3d
Device Boot Start End Blocks Id System
/dev/sdg1 * 63 208844 104391 83 Linux
/dev/sdg2 208845 4417874 2104515 82 Linux swap / Solaris
/dev/sdg3 4417875 209230559 102406342+ 83 Linux
/dev/sdg4 209230560 976768064 383768752+ 83 Linux
Screengrab of my VirtualBox storage setup (just for giggles):
My /etc/mkinitcpio.conf:
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES=""
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run first, so it may be used to
# override the actual binaries used in a given hook.
# (Existing files are NOT overwritten if already added)
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options
# like so:
# FILES="/etc/modprobe.d/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS="base udev autodetect pata scsi sata filesystems"
## This is identical to the above, except the old ide subsystem is
## used for IDE devices instead of the new pata subsystem.
# HOOKS="base udev autodetect ide scsi sata filesystems"
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS="base udev pata scsi sata usb filesystems"
## This setup assembles a pata mdadm array with an encrypted root FS.
## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
# HOOKS="base udev pata mdadm encrypt filesystems"
## This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev usb lvm2 filesystems"
# Tried this line instead -- didn't work either
#HOOKS="base udev usb autodetect pata scsi sata filesystems usbinput"
HOOKS="base udev usb sata filesystems"
# COMPRESSION
# Use this to compress the initramfs image. With kernels earlier than
# 2.6.30, only gzip is supported, which is also the default. Newer kernels
# support gzip, bzip2 and lzma. Kernels 2.6.38 and later support xz
# compression.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""
My GRUB menu.lst:
# Config file for GRUB - The GNU GRand Unified Bootloader
# /boot/grub/menu.lst
# DEVICE NAME CONVERSIONS
# Linux Grub
# /dev/fd0 (fd0)
# /dev/sda (hd0)
# /dev/sdb2 (hd1,1)
# /dev/sda3 (hd0,2)
# FRAMEBUFFER RESOLUTION SETTINGS
# +-------------------------------------------------+
# | 640x480 800x600 1024x768 1280x1024
# ----+--------------------------------------------
# 256 | 0x301=769 0x303=771 0x305=773 0x307=775
# 32K | 0x310=784 0x313=787 0x316=790 0x319=793
# 64K | 0x311=785 0x314=788 0x317=791 0x31A=794
# 16M | 0x312=786 0x315=789 0x318=792 0x31B=795
# +-------------------------------------------------+
# for more details and different resolutions see
# https://wiki.archlinux.org/index.php/GRUB#Framebuffer_resolution
# general configuration:
timeout 5
default 0
color light-blue/black light-cyan/blue
# boot sections follow
# each is implicitly numbered from 0 in the order of appearance below
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
# (0) Arch Linux
title Arch Linux
root (hd0,0)
kernel /vmlinuz-linux root=/dev/disk/by-uuid/b4a677d0-cb0d-4acd-bb09-2dc2f4b9501f ro
initrd /initramfs-linux.img
# (1) Arch Linux
title Arch Linux Fallback
root (hd0,0)
kernel /vmlinuz-linux root=/dev/disk/by-uuid/b4a677d0-cb0d-4acd-bb09-2dc2f4b9501f ro
initrd /initramfs-linux-fallback.img
# (2) Windows
#title Windows
#rootnoverify (hd0,0)
#makeactive
#chainloader +1
Last edited by UncleNinja (2011-12-02 15:33:21)

UncleNinja wrote:
skunktrader wrote:https://bugs.archlinux.org/task/27385
Perfect! Thank you!
Would it be safe to copy over the version from HEAD into my mkinitcpio?
EDIT: nevermind, derp derp the package is updated
EDIT again: Actually, it's not.
I copied over the init_functions in HEAD into /lib/initcpio/init_functions and rebuilt the initramfs. It worked!
Thanks guys!
Last edited by UncleNinja (2011-12-02 15:35:20)

SQL Server Agent running SSIS package fails Unable to determine if the owner of job has server access

I have a web application developed through VS 2012 which has a button on a form that when operated starts a SQL Server agent job on the server that runs an SSIS package. The website and the instance of SQL Server with the agent and SSIS package are
on the same windows 2008 r2 server. When the button is operated no exceptions are raised but the SSIS package did not execute.
When I look in the logfileviewer at the job history of the sql server agent job I see that the job failed with message...
The job failed. Unable to determine if the owner (DOMAINNAME\userid) of job runWebDevSmall has server access (reason: Could not obtain information about Windows NT group/user 'DOMAINNAME\userid'<c/> error code 0x6e. [SQLSTATE 42000] (Error 15404)).,00:00:00,0,0,,,,0
...even though DOMAINNAME\userid is in the logins for the sql server and has admin authorities.
Could someone show me what I need to do to get this to run? Thanks tonnes in advance for any help, Roscoe

This can happen when the network is too slow to allow a timely completion of the verification. Or the account running has no such right.
I suggest you try using the SA account for the job as it does not require to poll the AD.
Arthur My Blog

Maintain the acct key and accruals/provisions in the calculation schema

Dear All,
I have a problem during invoice posting.
I create a new freight condition type & assigned it to the calculation schema. I also create a new account key & assigned to the calculation schema in accrual keys. Then done OBYC settings. During MIGO, its working fine. But when i post the Miro against po, giving an error msg., "Maintain the acct key and accruals/provisions in the calculation schema, Message no. M8434"
plz help me to solve this issue.

Have you ticked the 'Acruals' in control data 2 in M/06 for this condition.
Regards,
Piyush

Maintain the acct key and acurals/provisions in calculation schema-MIRO

Hi,
In PO we have maintained different delivery condition.
When we are doing MIRO we are getting error "maintain the acct key and acurals/provisions in calculation schema" for condition type YLBB and YLBE.
However we have checked condition type and calulation schema and found that acct key and accurals maintained.
YLB9     BivacInspec.fee/Quan
YLBB     LPRC charges/Quant.
YLBC     Port charges/Quant.
YLBE     Clearing Charges/Qt.
Please suggest somesolution.
Thanks
Ashok

Hi Ashok,
In M/08 check whether   acct key and acurals/provisions in calculation schema" for condition type YLBB and YLBE are maintained or not.
Also if they are maintained there then check in M/06 for condition type YLBB and YLBE , whether accurals check box are checked or not...If not check and then try.
Cheers!!!
Utsav

Conditions in Calculation Schema not reflecting in Purch Info Record

Hi,
We are using calculation procedure TAXIN.
We have maintained Calculation Schema & maintained required conditions.
When we checked for maintaining these conditions in Purchasing Info Record, (Transaction Code - ME11 / ME12), these conditions are not appearing in the info record. But, the conditions appearing in the info record are not same as those in the Calculation Schema.
Also, the conditions maintained in Info Record are not getting copied to Purchase Order (except Base Price P000).
What could be the reason behind this? How to correct the same?
Regards,
Prashant Kolhatkar

Tax procedure condtions will not appear in the info record. for the conditon which is not reflecting in the PO, you may check in inforecord whether there is a check mark in condition record saved for approval; if so it is deleted

Unable to determine a calculation schema

Similar Messages

Maybe you are looking for