Configuration and tables

Hi Every One,
If I am configuring standard "OR"(copying "OR"), then do I have to make any changes in the sales order tables, if no changes are required to be done in standard "OR"?.
If change are to be made in "OR", then how do I make these changes.
I would be thankful, if you can explain these problems to me in details.
As ever , obliged .
VM
Edited by: VIKRAM MEHTA on Sep 19, 2008 12:14 AM

Step 1: Sales Document Type
IMG > Sales and Distribution > Sales > Sales Documents >
Sales Document Header:
1. Sales Document Type:The sales document types represent the different business transactions, such as Inquiry, Quotation, Sales Order, etc. To create new sales order type, always copy as with reference to similar sales order. If possible use standard sales order.2. Define Number Ranges For Sales Documents: Maintain number range with discussion with core team.
3. Assign Sales Area To Sales Document Types:
A. Combine sales organizations / Combine distribution channels / Combine divisions: Ensure to maintain these, else Sales Order creation will give error.
B. Assign sales order types permitted for sales areas: Assign only required Sales Order Types to required Sales Area. This will minimize selection of Sales Order Type as per sales area.
Sales Document Item:
1. Define Item Categories: If possible use Standard Item Category. Incase if required to create new, copy as from standard & maintain New.
2. Assign Item Categories: If possible, use standard. Formula for deriving item category: Sales Document Type + Item Category Group + Usage + Higher Level Item Category = Item Category
Schedule Line:
1. Define Schedule Line Categories: If possible use Standard Schedule Lines. Incase if required to create new, copy as from standard & maintain New.
2. Assign Schedule Line Categories: If possible, use standard. Formula for deriving Schedule Line: Item Category + MRP Type / No MRP Type.
Step 2:
IMG > Logistic Execution > Shipping > Deliveries >
1. Define Delivery Types: If possible use Standard Delivery Type. Incase if required to create new, copy as from standard & maintain New.
2. Define Item Categories for Deliveries: If possible use Standard Item Categories for Delivery Type. Incase if required to create new, copy as from standard & maintain New.
3. Define Number Ranges for Deliveries: Ensure to maintain number range.
Step 3:
IMG > Sales and Distribution > Billing >
1. Define Billing Types: If possible use Standard Billing Type. Incase if required to create new, copy as from standard & maintain New.
2. Define Number Range For Billing Documents: Ensure to maintain number range.
3. Maintain Copying Control For Billing Documents: Maintain relevant copy controls such as Sales Order to Billing, Deliver to Billing, etc.
Note: Ensure that Copy Control settings are done
Sales Order to Sales Order (QT --> OR): VTAA
Sales Order to Delivery (OR --> LF): VTLA
Sales Order to Billing (OR --> F1): VTFA
Delivery to Billing(LF --> F2): VTFL
Billing to Sales Order (F2 --> RE): VTAF
The configuration differs from scenario to scenario & requirement of the client.
Regards,
Rajesh Banka

Similar Messages

  • SAP PSCD configuration and TABLES

    hi all,
    I have alot of text information on SAP PSCD, but I am unable to find anything on transactions codes, table names config guides?
    can someone advice or point me to the correct direction?
    thanks

    Hi
    Have a look at the wiki page for Public Sector. It contains some links to SAP documentation, online help, Education, etc
    [http://wiki.sdn.sap.com/wiki/display/PS/Public+Sector]
    Please follow the engagement rules in order to find out how to post questions to the Forum
    [http://wiki.sdn.sap.com/wiki/display/HOME/Rules%20of%20Engagement]
    regards
    Mar

  • AAMEE 3.1 deployment get stuck at configuring and quits.

    Hello,
    I made a 32bit deployment of Adobe and when I test it out on my PC with msiexec with borwsers all off and no adobe applications running it makes it half way throgh configuring and then stops and the stats bar goes back to the start and it quits.
    Bellow is the PDApp.log, any help would be grateful.
    Mike
    11/13/2013 15:26:20 [INFO] DeploymentManager - Build Version - 3.1.105.0
    11/13/2013 15:26:20 [INFO] DeploymentManager - Logging Level verbosity Set  to 4
    11/13/2013 15:26:20 [INFO] DeploymentManager - Executing immediate custom action for install mode.
    11/13/2013 15:26:20 [INFO] DeploymentManager - The CustomActionData string is : mode=install;sourceDir=d:\32bit Adobe2\Build\;installDir=;origDB=d:\32bit Adobe2\Build\32bit Adobe2.msi
    11/13/2013 15:26:20 [INFO] DeploymentManager - Successfully executed the immediate custom action for install mode .
    11/13/2013 15:26:25 [INFO] DeploymentManager - Build Version - 3.1.105.0
    11/13/2013 15:26:25 [INFO] DeploymentManager - Logging Level verbosity Set  to 4
    11/13/2013 15:26:25 [INFO] DeploymentManager - Executing the deferred custom action.
    11/13/2013 15:26:25 [INFO] DeploymentManager - Obtained the following as CustomActionData
    11/13/2013 15:26:25 [INFO] DeploymentManager - mode=install;sourceDir=d:\32bit Adobe2\Build\;installDir=;origDB=d:\32bit Adobe2\Build\32bit Adobe2.msi
    11/13/2013 15:26:25 [INFO] DeploymentManager - mode=install;sourceDir=d:\32bit Adobe2\Build\;installDir=;origDB=d:\32bit Adobe2\Build\32bit Adobe2.msi
    11/13/2013 15:26:25 [INFO] DeploymentManager - Original database path is : d:\32bit Adobe2\Build\32bit Adobe2.msi
    11/13/2013 15:26:25 [INFO] DeploymentManager - OptionXML saved at location :: C:\Users\mseddon\AppData\Local\Temp\{386867CE-0461-4FC3-83EA-466DEF7D5226}\\{0CB84CF3-741 B-4DDA-B3DF-B3066BA0B327}
    11/13/2013 15:26:25 [INFO] DeploymentManager - Build Version - 3.1.105.0
    11/13/2013 15:26:25 [INFO] DeploymentManager - Logging Level verbosity Set  to 4
    11/13/2013 15:26:25 [INFO] DeploymentManager - Initializing Custom Action Data from parameters
    11/13/2013 15:26:25 [INFO] Utilities - Folder does not exist
    11/13/2013 15:26:25 [INFO] DeploymentManager - Provisioning Tool path is (C:\Users\mseddon\AppData\Local\Temp\{386867CE-0461-4FC3-83EA-466DEF7D5226}\\{3E60E409-97 DF-4D53-A4EB-846FB440181F}).
    11/13/2013 15:26:25 [INFO] DeploymentManager - Starting to run the custom action for install mode
    11/13/2013 15:26:25 [INFO] DeploymentManager - STEP 1: Starting to parse Option XML.
    11/13/2013 15:26:25 [INFO] DeploymentManager - Deployment XML created at path :: C:\Users\mseddon\AppData\Local\Temp\{1B76C0EA-C5CA-468A-AC2E-AF580CF03F2E}\\{65525300-78B 5-4102-95D3-6980332AB10A}
    11/13/2013 15:26:25 [INFO] DeploymentManager - Deployment Manager is running in Install Mode.
    11/13/2013 15:26:25 [INFO] DeploymentManager - Self-Update BootStrapper Relative Path doesn't exist.
    11/13/2013 15:26:25 [INFO] DeploymentManager - Override XML created at path :: C:\Users\mseddon\AppData\Local\Temp\{1B76C0EA-C5CA-468A-AC2E-AF580CF03F2E}\\{27B51110-840 2-40F6-AD4D-7C85BC150CF0}
    11/13/2013 15:26:25 [INFO] DeploymentManager - No of updates found (11).
    11/13/2013 15:26:25 [INFO] DeploymentManager - STEP 2: Starting to launch media Bootstrapper.
    11/13/2013 15:26:25 [INFO] DeploymentManager - Bootstrapper launch location is :: d:\32bit Adobe2\Build\Setup\Set-up.dat
    11/13/2013 15:26:25 [INFO] Setup - Build Version - 6.0.335.0
    11/13/2013 15:26:25 [INFO] Setup - Logging Level verbosity Set  to 4
    11/13/2013 15:26:25 [INFO] Setup - Start Adobe Setup
    11/13/2013 15:26:25 [INFO] Setup - TimeLog: Bootstrapper Start
    11/13/2013 15:26:25 [INFO] Setup - TimeLog: Start initial checks
    11/13/2013 15:26:25 [INFO] Setup - Action specified - "install"
    11/13/2013 15:26:25 [ERROR] Setup - Error parsing command line arguments at - "DISABLE_CCM_DESKTOPSHORTCUT".
    Expected arguments are -
              --mode=silent
              --overrideFile="<FilePath>"
    11/13/2013 15:26:25 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Setup\resources\setup.xml
    11/13/2013 15:26:25 [INFO] PIM - XML is valid
    11/13/2013 15:26:25 [WARN] PIM - Failed to find Node
    11/13/2013 15:26:25 [INFO] Setup - Found 6 packages in setup manifest
    11/13/2013 15:26:25 [INFO] Utilities - Semaphore is not locked
    11/13/2013 15:26:25 [INFO] PIM - Build Version - 6.0.335.0
    11/13/2013 15:26:25 [INFO] PIM - Logging Level verbosity Set  to 4
    11/13/2013 15:26:25 [INFO] Utilities - File does not exist
    11/13/2013 15:26:25 [INFO] Utilities - File does not exist
    11/13/2013 15:26:25 [INFO] PIM - Build Version - 6.0.335.0
    11/13/2013 15:26:25 [INFO] PIM - Logging Level verbosity Set  to 4
    11/13/2013 15:26:25 [INFO] PIM - CREATE PIM Instance ...
    11/13/2013 15:26:25 [INFO] Utilities - File does not exist
    11/13/2013 15:26:25 [INFO] Utilities - File does not exist
    11/13/2013 15:26:25 [INFO] PIM - trying to createOrUpdatePIMDbSchema.
    11/13/2013 15:26:25 [INFO] PIM - SUCCESS Created Tables.
    11/13/2013 15:26:25 [INFO] PIM - PIM Database is Up To Date.
    11/13/2013 15:26:25 [INFO] PIM - Updater Inventory location:d:\32bit Adobe2\Build\Setup\resources\updaterinventory.dll
    11/13/2013 15:26:25 [INFO] PIM - Acquired System level ACF lock ...
    11/13/2013 15:26:25 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Setup\packages\core\PDApp.pimx
    11/13/2013 15:26:25 [INFO] PIM - XML is valid
    11/13/2013 15:26:25 [WARN] PIM - Failed to find Node
    11/13/2013 15:26:25 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Setup\packages\D6\D6.pimx
    11/13/2013 15:26:25 [INFO] PIM - XML is valid
    11/13/2013 15:26:25 [WARN] PIM - Failed to find Node
    11/13/2013 15:26:25 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Setup\packages\DECore\DECore.pimx
    11/13/2013 15:26:25 [INFO] PIM - XML is valid
    11/13/2013 15:26:25 [WARN] PIM - Failed to find Node
    11/13/2013 15:26:25 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Setup\packages\DWA\DWA.pimx
    11/13/2013 15:26:25 [INFO] PIM - XML is valid
    11/13/2013 15:26:25 [WARN] PIM - Failed to find Node
    11/13/2013 15:26:25 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Setup\packages\P6\P6.pimx
    11/13/2013 15:26:25 [INFO] PIM - XML is valid
    11/13/2013 15:26:25 [WARN] PIM - Failed to find Node
    11/13/2013 15:26:25 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Setup\packages\LWA\LWA.pimx
    11/13/2013 15:26:25 [INFO] PIM - XML is valid
    11/13/2013 15:26:25 [WARN] PIM - Failed to find Node
    11/13/2013 15:26:25 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Setup\packages\UWA\UWA.pimx
    11/13/2013 15:26:25 [INFO] PIM - XML is valid
    11/13/2013 15:26:25 [WARN] PIM - Failed to find Node
    11/13/2013 15:26:25 [INFO] PIM - pim_haveEnoughDiskSpaceToInstallPackages reqSize ... 104237697
    11/13/2013 15:26:25 [INFO] Setup - TimeLog: End initial checks
    11/13/2013 15:26:25 [INFO] Setup - TimeLog: Begin Installing
    11/13/2013 15:26:25 [INFO] Setup - Start Installing core package - d:\32bit Adobe2\Build\Setup\packages\core\PDApp.pimx
    11/13/2013 15:26:25 [INFO] PIM - START installPackage at file d:\32bit Adobe2\Build\Setup\packages\core\PDApp.pimx
    11/13/2013 15:26:25 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Setup\packages\core\PDApp.pimx
    11/13/2013 15:26:25 [INFO] PIM - XML is valid
    11/13/2013 15:26:25 [WARN] PIM - Failed to find Node
    11/13/2013 15:26:25 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Setup\packages\core\PDApp.pimx'
    11/13/2013 15:26:25 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Setup\packages\core\PDApp.pima'
    11/13/2013 15:26:26 [INFO] PIM - SUCCESS insertPackageUpdateList.
    11/13/2013 15:26:26 [WARN] PIM - Failed to find Node
    11/13/2013 15:26:26 [INFO] PIM - SUCCESS insertAppletRegInfoList.
    11/13/2013 15:26:29 [INFO] Utilities - File does not exist
    11/13/2013 15:26:29 [INFO] PIM - SUCCESS installPackage at file d:\32bit Adobe2\Build\Setup\packages\core\PDApp.pimx.
    11/13/2013 15:26:29 [INFO] Setup - Finished Installing core package - d:\32bit Adobe2\Build\Setup\packages\core\PDApp.pimx, Return status: 0
    11/13/2013 15:26:29 [INFO] Setup - Start Installing package - d:\32bit Adobe2\Build\Setup\packages\D6\D6.pimx
    11/13/2013 15:26:29 [INFO] PIM - START installPackage at file d:\32bit Adobe2\Build\Setup\packages\D6\D6.pimx
    11/13/2013 15:26:29 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Setup\packages\D6\D6.pimx
    11/13/2013 15:26:29 [INFO] PIM - XML is valid
    11/13/2013 15:26:29 [WARN] PIM - Failed to find Node
    11/13/2013 15:26:29 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Setup\packages\D6\D6.pimx'
    11/13/2013 15:26:29 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Setup\packages\D6\D6.pima'
    11/13/2013 15:26:29 [INFO] PIM - SUCCESS insertPackageUpdateList.
    11/13/2013 15:26:29 [INFO] PIM - SUCCESS insertAppletRegInfoList.
    11/13/2013 15:26:30 [INFO] Utilities - File does not exist
    11/13/2013 15:26:31 [INFO] PIM - SUCCESS installPackage at file d:\32bit Adobe2\Build\Setup\packages\D6\D6.pimx.
    11/13/2013 15:26:31 [INFO] Setup - Finished Installing package - d:\32bit Adobe2\Build\Setup\packages\D6\D6.pimx
    11/13/2013 15:26:31 [INFO] Setup - Start Installing package - d:\32bit Adobe2\Build\Setup\packages\DECore\DECore.pimx
    11/13/2013 15:26:31 [INFO] PIM - START installPackage at file d:\32bit Adobe2\Build\Setup\packages\DECore\DECore.pimx
    11/13/2013 15:26:31 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Setup\packages\DECore\DECore.pimx
    11/13/2013 15:26:31 [INFO] PIM - XML is valid
    11/13/2013 15:26:31 [WARN] PIM - Failed to find Node
    11/13/2013 15:26:31 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Setup\packages\DECore\DECore.pimx'
    11/13/2013 15:26:31 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Setup\packages\DECore\DECore.pima'
    11/13/2013 15:26:31 [INFO] PIM - SUCCESS insertPackageUpdateList.
    11/13/2013 15:26:31 [WARN] PIM - Failed to find Node
    11/13/2013 15:26:31 [INFO] PIM - SUCCESS insertAppletRegInfoList.
    11/13/2013 15:26:33 [INFO] Utilities - File does not exist
    11/13/2013 15:26:33 [INFO] PIM - SUCCESS installPackage at file d:\32bit Adobe2\Build\Setup\packages\DECore\DECore.pimx.
    11/13/2013 15:26:33 [INFO] Setup - Finished Installing package - d:\32bit Adobe2\Build\Setup\packages\DECore\DECore.pimx
    11/13/2013 15:26:33 [INFO] Setup - Start Installing package - d:\32bit Adobe2\Build\Setup\packages\DWA\DWA.pimx
    11/13/2013 15:26:33 [INFO] PIM - START installPackage at file d:\32bit Adobe2\Build\Setup\packages\DWA\DWA.pimx
    11/13/2013 15:26:33 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Setup\packages\DWA\DWA.pimx
    11/13/2013 15:26:33 [INFO] PIM - XML is valid
    11/13/2013 15:26:33 [WARN] PIM - Failed to find Node
    11/13/2013 15:26:33 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Setup\packages\DWA\DWA.pimx'
    11/13/2013 15:26:33 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Setup\packages\DWA\DWA.pima'
    11/13/2013 15:26:33 [INFO] PIM - SUCCESS insertPackageUpdateList.
    11/13/2013 15:26:33 [INFO] PIM - SUCCESS insertAppletRegInfoList.
    11/13/2013 15:26:34 [INFO] Utilities - File does not exist
    11/13/2013 15:26:34 [INFO] PIM - SUCCESS installPackage at file d:\32bit Adobe2\Build\Setup\packages\DWA\DWA.pimx.
    11/13/2013 15:26:34 [INFO] Setup - Finished Installing package - d:\32bit Adobe2\Build\Setup\packages\DWA\DWA.pimx
    11/13/2013 15:26:34 [INFO] Setup - Start Installing package - d:\32bit Adobe2\Build\Setup\packages\P6\P6.pimx
    11/13/2013 15:26:34 [INFO] PIM - START installPackage at file d:\32bit Adobe2\Build\Setup\packages\P6\P6.pimx
    11/13/2013 15:26:34 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Setup\packages\P6\P6.pimx
    11/13/2013 15:26:34 [INFO] PIM - XML is valid
    11/13/2013 15:26:34 [WARN] PIM - Failed to find Node
    11/13/2013 15:26:34 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Setup\packages\P6\P6.pimx'
    11/13/2013 15:26:34 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Setup\packages\P6\P6.pima'
    11/13/2013 15:26:34 [INFO] PIM - SUCCESS insertPackageUpdateList.
    11/13/2013 15:26:34 [INFO] PIM - SUCCESS insertAppletRegInfoList.
    11/13/2013 15:26:37 [INFO] Utilities - File does not exist
    11/13/2013 15:26:37 [INFO] PIM - SUCCESS installPackage at file d:\32bit Adobe2\Build\Setup\packages\P6\P6.pimx.
    11/13/2013 15:26:37 [INFO] Setup - Finished Installing package - d:\32bit Adobe2\Build\Setup\packages\P6\P6.pimx
    11/13/2013 15:26:37 [INFO] Setup - Start Installing package - d:\32bit Adobe2\Build\Setup\packages\LWA\LWA.pimx
    11/13/2013 15:26:37 [INFO] PIM - START installPackage at file d:\32bit Adobe2\Build\Setup\packages\LWA\LWA.pimx
    11/13/2013 15:26:37 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Setup\packages\LWA\LWA.pimx
    11/13/2013 15:26:37 [INFO] PIM - XML is valid
    11/13/2013 15:26:37 [WARN] PIM - Failed to find Node
    11/13/2013 15:26:37 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Setup\packages\LWA\LWA.pimx'
    11/13/2013 15:26:37 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Setup\packages\LWA\LWA.pima'
    11/13/2013 15:26:37 [INFO] PIM - SUCCESS insertPackageUpdateList.
    11/13/2013 15:26:37 [INFO] PIM - SUCCESS insertAppletRegInfoList.
    11/13/2013 15:26:39 [INFO] Utilities - File does not exist
    11/13/2013 15:26:39 [INFO] PIM - SUCCESS installPackage at file d:\32bit Adobe2\Build\Setup\packages\LWA\LWA.pimx.
    11/13/2013 15:26:39 [INFO] Setup - Finished Installing package - d:\32bit Adobe2\Build\Setup\packages\LWA\LWA.pimx
    11/13/2013 15:26:39 [INFO] Setup - Start Installing package - d:\32bit Adobe2\Build\Setup\packages\UWA\UWA.pimx
    11/13/2013 15:26:39 [INFO] PIM - START installPackage at file d:\32bit Adobe2\Build\Setup\packages\UWA\UWA.pimx
    11/13/2013 15:26:39 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Setup\packages\UWA\UWA.pimx
    11/13/2013 15:26:40 [INFO] PIM - XML is valid
    11/13/2013 15:26:40 [WARN] PIM - Failed to find Node
    11/13/2013 15:26:40 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Setup\packages\UWA\UWA.pimx'
    11/13/2013 15:26:40 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Setup\packages\UWA\UWA.pima'
    11/13/2013 15:26:40 [INFO] PIM - SUCCESS insertPackageUpdateList.
    11/13/2013 15:26:40 [INFO] PIM - SUCCESS insertAppletRegInfoList.
    11/13/2013 15:26:41 [INFO] Utilities - File does not exist
    11/13/2013 15:26:42 [INFO] PIM - SUCCESS installPackage at file d:\32bit Adobe2\Build\Setup\packages\UWA\UWA.pimx.
    11/13/2013 15:26:42 [INFO] Setup - Finished Installing package - d:\32bit Adobe2\Build\Setup\packages\UWA\UWA.pimx
    11/13/2013 15:26:42 [INFO] PIM - Processing ... _pimCreateOrUpdateAAMInventory
    11/13/2013 15:26:42 [INFO] PIM - Return ... SUCCESS _pimCreateOrUpdateAAMInventory
    11/13/2013 15:26:42 [INFO] Setup - TimeLog: End Installing. Now launching PDApp
    11/13/2013 15:26:42 [INFO] Setup - Deployment File Path not specified in command line arguments. Skipping payload deployment part
    11/13/2013 15:26:42 [INFO] Setup - =================  End Adobe Setup. Exit code: 0  =================
    11/13/2013 15:26:42 [INFO] PIM - PIMSqlite closeDB status 0
    11/13/2013 15:26:42 [INFO] PIM - FREE PIM Instance ...
    11/13/2013 15:26:42 [INFO] DeploymentManager - Build Version - 3.1.105.0
    11/13/2013 15:26:42 [INFO] DeploymentManager - Logging Level verbosity Set  to 4
    11/13/2013 15:26:42 [INFO] DeploymentManager - The return code from the Bootstrapper Process is (0).
    11/13/2013 15:26:42 [INFO] DeploymentManager - STEP 3: Starting to launch ASU AAM.
    11/13/2013 15:26:42 [INFO] DeploymentManager - Bootstrapper launch location is :: d:\32bit Adobe2\Build\ASU\Set-up.dat
    11/13/2013 15:26:43 [INFO] Setup - Build Version - 6.2.136.0
    11/13/2013 15:26:43 [INFO] Setup - Logging Level verbosity Set  to 4
    11/13/2013 15:26:43 [INFO] Setup - Start Adobe Setup
    11/13/2013 15:26:43 [INFO] Setup - TimeLog: Bootstrapper Start
    11/13/2013 15:26:43 [INFO] Setup - TimeLog: Start initial checks
    11/13/2013 15:26:43 [INFO] Setup - Action specified - "install"
    11/13/2013 15:26:43 [ERROR] Setup - Error parsing command line arguments at - "DISABLE_CCM_DESKTOPSHORTCUT".
    Expected arguments are -
              --mode=silent
              --overrideFile="<FilePath>"
    11/13/2013 15:26:43 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\ASU\resources\setup.xml
    11/13/2013 15:26:43 [INFO] PIM - XML is valid
    11/13/2013 15:26:43 [WARN] PIM - Failed to find Node
    11/13/2013 15:26:43 [INFO] Setup - Found 7 packages in setup manifest

    11/13/2013 15:27:08 [INFO] Utilities - Semaphore is not locked
    11/13/2013 15:27:08 [INFO] PIM - Build Version - 6.2.136.0
    11/13/2013 15:27:08 [INFO] PIM - Logging Level verbosity Set  to 4
    11/13/2013 15:27:08 [INFO] Utilities - File does not exist
    11/13/2013 15:27:08 [INFO] Utilities - File does not exist
    11/13/2013 15:27:08 [INFO] PIM - Build Version - 6.2.136.0
    11/13/2013 15:27:08 [INFO] PIM - Logging Level verbosity Set  to 4
    11/13/2013 15:27:08 [INFO] PIM - CREATE PIM Instance ...
    11/13/2013 15:27:08 [INFO] Utilities - File does not exist
    11/13/2013 15:27:08 [INFO] PIM - trying to createOrUpdatePIMDbSchema.
    11/13/2013 15:27:08 [INFO] PIM - Current db schema version on machine 1.
    11/13/2013 15:27:08 [INFO] PIM - Current db schema version to install 1.
    11/13/2013 15:27:08 [INFO] PIM - PIM DB Schema is up to date. Current schema version is 1.
    11/13/2013 15:27:08 [INFO] PIM - PIM Database is Up To Date.
    11/13/2013 15:27:08 [INFO] PIM - Updater Inventory location:d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\resources\updaterinventory.dll
    11/13/2013 15:27:08 [INFO] PIM - Acquired System level ACF lock ...
    11/13/2013 15:27:08 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\core\PDApp.pimx
    11/13/2013 15:27:08 [INFO] PIM - XML is valid
    11/13/2013 15:27:08 [WARN] PIM - Failed to find Node
    11/13/2013 15:27:08 [INFO] PIM - Package id 5AA1D762-31AF-4FC3-A0C0-66BF663B2117 is already installed
    11/13/2013 15:27:08 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\D6\D6.pimx
    11/13/2013 15:27:08 [INFO] PIM - XML is valid
    11/13/2013 15:27:08 [WARN] PIM - Failed to find Node
    11/13/2013 15:27:08 [INFO] PIM - Package id 54FD72DC-72EC-4CDC-8828-F07C4E9E6FA2 is already installed
    11/13/2013 15:27:08 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\DECore\DECore.pimx
    11/13/2013 15:27:08 [INFO] PIM - XML is valid
    11/13/2013 15:27:08 [WARN] PIM - Failed to find Node
    11/13/2013 15:27:08 [INFO] PIM - Package id 6D2A548B-C50D-46BA-B83E-C8199C6A9406 is already installed
    11/13/2013 15:27:08 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\DWA\DWA.pimx
    11/13/2013 15:27:08 [INFO] PIM - XML is valid
    11/13/2013 15:27:08 [WARN] PIM - Failed to find Node
    11/13/2013 15:27:08 [INFO] PIM - Package id 99477136-88AD-496B-9551-BAE72699A32C is already installed
    11/13/2013 15:27:08 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\P6\P6.pimx
    11/13/2013 15:27:08 [INFO] PIM - XML is valid
    11/13/2013 15:27:08 [WARN] PIM - Failed to find Node
    11/13/2013 15:27:08 [INFO] PIM - Package id FAFC744B-DDFB-4097-A41D-7E9539FEBAF9 is already installed
    11/13/2013 15:27:08 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\LWA\LWA.pimx
    11/13/2013 15:27:08 [INFO] PIM - XML is valid
    11/13/2013 15:27:08 [WARN] PIM - Failed to find Node
    11/13/2013 15:27:08 [INFO] PIM - Package id B322281B-C04F-438E-82D7-7DA34A359526 is already installed
    11/13/2013 15:27:08 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\UWA\UWA.pimx
    11/13/2013 15:27:08 [INFO] PIM - XML is valid
    11/13/2013 15:27:08 [WARN] PIM - Failed to find Node
    11/13/2013 15:27:08 [INFO] PIM - Package id B1313DE3-08DF-4834-91D9-CBD1A91488E5 is already installed
    11/13/2013 15:27:08 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\CCM\CCM.pimx
    11/13/2013 15:27:08 [INFO] PIM - XML is valid
    11/13/2013 15:27:08 [WARN] PIM - Failed to find Node
    11/13/2013 15:27:08 [INFO] PIM - Package id F0158AAB-0779-4B40-A07D-3F2A21D47E74 is already installed
    11/13/2013 15:27:08 [INFO] PIM - pim_haveEnoughDiskSpaceToInstallPackages reqSize ... 29928536
    11/13/2013 15:27:08 [INFO] Setup - TimeLog: End initial checks
    11/13/2013 15:27:08 [INFO] Setup - TimeLog: Begin Installing
    11/13/2013 15:27:08 [INFO] Setup - Start Installing core package - d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\core\PDApp.pimx
    11/13/2013 15:27:08 [INFO] PIM - START installPackage at file d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\core\PDApp.pimx
    11/13/2013 15:27:08 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\core\PDApp.pimx
    11/13/2013 15:27:08 [INFO] PIM - XML is valid
    11/13/2013 15:27:08 [WARN] PIM - Failed to find Node
    11/13/2013 15:27:08 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\core\PDApp.pimx'
    11/13/2013 15:27:08 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\core\PDApp.pima'
    11/13/2013 15:27:08 [INFO] PIM - Package id 5AA1D762-31AF-4FC3-A0C0-66BF663B2117 is already installed
    11/13/2013 15:27:08 [INFO] PIM - SUCCESS deleteAppletRegInfoRecords.
    11/13/2013 15:27:08 [INFO] PIM - SUCCESS deletePackageUpgradeInfoRecords.
    11/13/2013 15:27:08 [INFO] PIM - SUCCESS deletePackageInstallationInfoRecords.
    11/13/2013 15:27:08 [INFO] PIM - SUCCESS insertPackageUpdateList.
    11/13/2013 15:27:08 [WARN] PIM - Failed to find Node
    11/13/2013 15:27:08 [INFO] PIM - SUCCESS insertAppletRegInfoList.
    11/13/2013 15:27:08 [INFO] PIM - Backup Folder Created
    11/13/2013 15:27:12 [INFO] Utilities - File does not exist
    11/13/2013 15:27:12 [INFO] PIM - SUCCESS installPackage at file d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\core\PDApp.pimx.
    11/13/2013 15:27:13 [INFO] Setup - Finished Installing core package - d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\core\PDApp.pimx, Return status: 0
    11/13/2013 15:27:13 [INFO] Setup - Start Installing package - d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\D6\D6.pimx
    11/13/2013 15:27:13 [INFO] PIM - START installPackage at file d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\D6\D6.pimx
    11/13/2013 15:27:13 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\D6\D6.pimx
    11/13/2013 15:27:13 [INFO] PIM - XML is valid
    11/13/2013 15:27:13 [WARN] PIM - Failed to find Node
    11/13/2013 15:27:13 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\D6\D6.pimx'
    11/13/2013 15:27:13 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\D6\D6.pima'
    11/13/2013 15:27:13 [INFO] PIM - Package id 54FD72DC-72EC-4CDC-8828-F07C4E9E6FA2 is already installed
    11/13/2013 15:27:13 [INFO] PIM - SUCCESS deleteAppletRegInfoRecords.
    11/13/2013 15:27:13 [INFO] PIM - SUCCESS deletePackageUpgradeInfoRecords.
    11/13/2013 15:27:13 [INFO] PIM - SUCCESS deletePackageInstallationInfoRecords.
    11/13/2013 15:27:13 [INFO] PIM - SUCCESS insertPackageUpdateList.
    11/13/2013 15:27:13 [INFO] PIM - SUCCESS insertAppletRegInfoList.
    11/13/2013 15:27:13 [INFO] PIM - Backup Folder Created
    11/13/2013 15:27:13 [INFO] Utilities - File does not exist
    11/13/2013 15:27:14 [INFO] PIM - SUCCESS installPackage at file d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\D6\D6.pimx.
    11/13/2013 15:27:14 [INFO] Setup - Finished Installing package - d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\D6\D6.pimx
    11/13/2013 15:27:14 [INFO] Setup - Start Installing package - d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\DECore\DECore.pimx
    11/13/2013 15:27:14 [INFO] PIM - START installPackage at file d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\DECore\DECore.pimx
    11/13/2013 15:27:14 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\DECore\DECore.pimx
    11/13/2013 15:27:14 [INFO] PIM - XML is valid
    11/13/2013 15:27:14 [WARN] PIM - Failed to find Node
    11/13/2013 15:27:14 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\DECore\DECore.pimx'
    11/13/2013 15:27:14 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\DECore\DECore.pima'
    11/13/2013 15:27:14 [INFO] PIM - Package id 6D2A548B-C50D-46BA-B83E-C8199C6A9406 is already installed
    11/13/2013 15:27:14 [INFO] PIM - SUCCESS deleteAppletRegInfoRecords.
    11/13/2013 15:27:14 [INFO] PIM - SUCCESS deletePackageUpgradeInfoRecords.
    11/13/2013 15:27:14 [INFO] PIM - SUCCESS deletePackageInstallationInfoRecords.
    11/13/2013 15:27:14 [INFO] PIM - SUCCESS insertPackageUpdateList.
    11/13/2013 15:27:14 [WARN] PIM - Failed to find Node
    11/13/2013 15:27:14 [INFO] PIM - SUCCESS insertAppletRegInfoList.
    11/13/2013 15:27:14 [INFO] PIM - Backup Folder Created
    11/13/2013 15:27:16 [INFO] Utilities - File does not exist
    11/13/2013 15:27:17 [INFO] PIM - SUCCESS installPackage at file d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\DECore\DECore.pimx.
    11/13/2013 15:27:17 [INFO] Setup - Finished Installing package - d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\DECore\DECore.pimx
    11/13/2013 15:27:17 [INFO] Setup - Start Installing package - d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\DWA\DWA.pimx
    11/13/2013 15:27:17 [INFO] PIM - START installPackage at file d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\DWA\DWA.pimx
    11/13/2013 15:27:17 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\DWA\DWA.pimx
    11/13/2013 15:27:17 [INFO] PIM - XML is valid
    11/13/2013 15:27:17 [WARN] PIM - Failed to find Node
    11/13/2013 15:27:17 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\DWA\DWA.pimx'
    11/13/2013 15:27:17 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\DWA\DWA.pima'
    11/13/2013 15:27:17 [INFO] PIM - Package id 99477136-88AD-496B-9551-BAE72699A32C is already installed
    11/13/2013 15:27:17 [INFO] PIM - SUCCESS deleteAppletRegInfoRecords.
    11/13/2013 15:27:17 [INFO] PIM - SUCCESS deletePackageUpgradeInfoRecords.
    11/13/2013 15:27:17 [INFO] PIM - SUCCESS deletePackageInstallationInfoRecords.
    11/13/2013 15:27:17 [INFO] PIM - SUCCESS insertPackageUpdateList.
    11/13/2013 15:27:17 [INFO] PIM - SUCCESS insertAppletRegInfoList.
    11/13/2013 15:27:17 [INFO] PIM - Backup Folder Created
    11/13/2013 15:27:18 [INFO] Utilities - File does not exist
    11/13/2013 15:27:19 [INFO] PIM - SUCCESS installPackage at file d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\DWA\DWA.pimx.
    11/13/2013 15:27:19 [INFO] Setup - Finished Installing package - d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\DWA\DWA.pimx
    11/13/2013 15:27:19 [INFO] Setup - Start Installing package - d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\P6\P6.pimx
    11/13/2013 15:27:19 [INFO] PIM - START installPackage at file d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\P6\P6.pimx
    11/13/2013 15:27:19 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\P6\P6.pimx
    11/13/2013 15:27:19 [INFO] PIM - XML is valid
    11/13/2013 15:27:19 [WARN] PIM - Failed to find Node
    11/13/2013 15:27:19 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\P6\P6.pimx'
    11/13/2013 15:27:19 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\P6\P6.pima'
    11/13/2013 15:27:19 [INFO] PIM - Package id FAFC744B-DDFB-4097-A41D-7E9539FEBAF9 is already installed
    11/13/2013 15:27:19 [INFO] PIM - SUCCESS deleteAppletRegInfoRecords.
    11/13/2013 15:27:19 [INFO] PIM - SUCCESS deletePackageUpgradeInfoRecords.
    11/13/2013 15:27:19 [INFO] PIM - SUCCESS deletePackageInstallationInfoRecords.
    11/13/2013 15:27:19 [INFO] PIM - SUCCESS insertPackageUpdateList.
    11/13/2013 15:27:19 [INFO] PIM - SUCCESS insertAppletRegInfoList.
    11/13/2013 15:27:19 [INFO] PIM - Backup Folder Created
    11/13/2013 15:27:21 [INFO] Utilities - File does not exist
    11/13/2013 15:27:22 [INFO] PIM - SUCCESS installPackage at file d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\P6\P6.pimx.
    11/13/2013 15:27:22 [INFO] Setup - Finished Installing package - d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\P6\P6.pimx
    11/13/2013 15:27:22 [INFO] Setup - Start Installing package - d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\LWA\LWA.pimx
    11/13/2013 15:27:22 [INFO] PIM - START installPackage at file d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\LWA\LWA.pimx
    11/13/2013 15:27:22 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\LWA\LWA.pimx
    11/13/2013 15:27:22 [INFO] PIM - XML is valid
    11/13/2013 15:27:22 [WARN] PIM - Failed to find Node
    11/13/2013 15:27:22 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\LWA\LWA.pimx'
    11/13/2013 15:27:22 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\LWA\LWA.pima'
    11/13/2013 15:27:22 [INFO] PIM - Package id B322281B-C04F-438E-82D7-7DA34A359526 is already installed
    11/13/2013 15:27:22 [INFO] PIM - SUCCESS deleteAppletRegInfoRecords.
    11/13/2013 15:27:22 [INFO] PIM - SUCCESS deletePackageUpgradeInfoRecords.
    11/13/2013 15:27:22 [INFO] PIM - SUCCESS deletePackageInstallationInfoRecords.
    11/13/2013 15:27:22 [INFO] PIM - SUCCESS insertPackageUpdateList.
    11/13/2013 15:27:22 [INFO] PIM - SUCCESS insertAppletRegInfoList.
    11/13/2013 15:27:22 [INFO] PIM - Backup Folder Created
    11/13/2013 15:27:24 [INFO] Utilities - File does not exist
    11/13/2013 15:27:25 [INFO] PIM - SUCCESS installPackage at file d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\LWA\LWA.pimx.
    11/13/2013 15:27:25 [INFO] Setup - Finished Installing package - d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\LWA\LWA.pimx
    11/13/2013 15:27:25 [INFO] Setup - Start Installing package - d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\UWA\UWA.pimx
    11/13/2013 15:27:25 [INFO] PIM - START installPackage at file d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\UWA\UWA.pimx
    11/13/2013 15:27:25 [INFO] PIM - Trying to access xml at path:d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\UWA\UWA.pimx
    11/13/2013 15:27:25 [INFO] PIM - XML is valid
    11/13/2013 15:27:25 [WARN] PIM - Failed to find Node
    11/13/2013 15:27:25 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\UWA\UWA.pimx'
    11/13/2013 15:27:25 [INFO] PIM - Validating package file: 'd:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7\packages\UWA\UWA.pima'
    11/13/2013 15:27:25 [INFO] PIM - Package id B1313DE3-08DF-4834-91D9-CBD1A91488E5 is already installed
    11/13/2013 15:27:25 [INFO] PIM - SUCCESS deleteAppletRegInfoRecords.
    11/13/2013 15:27:25 [INFO] PIM - SUCCESS deletePackageUpgradeInfoRecords.
    11/13/2013 15:27:25 [INFO] PIM - SUCCESS deletePackageInstallationInfoRecords.
    11/13/2013 15:27:25 [INFO] PIM - SUCCESS insertPackageUpdateList.
    11/13/2013 15:27:25 [INFO] PIM - SUCCESS insertAppletRegInfoList.
    11/13/2013 15:27:25 [INFO] PIM - Backup Folder Created
    11/13/2013 15:27:27 [INFO] Utilities - File does not exist
    11/13/2013 15:27:27 [INFO] PIM - SUCCESS installPackage at file d:\32bit Adobe2\Build\Patches\AdobeApplicationManager-1.0_update7

  • How do I integrate Configurator and iPad Electronic Flight Bags with applications that utilize a third-party license and subscription that is outside of iTunes?

    I am the EFB (Electronic Flight Bag) Manager for a small aviation company that are using 10 iPad with Retina Display as approved in-cockpit EFBs.  Our plan is to configure and manage these iPad EFBs with Apple Configurator 1.3.  We also use 2 third-party applications for charts, aviation weather, and other aviation functions that depend on a seperate license and subscription with the vendor outside of iTunes.  What I am finding through my new education in Configurator is that there does not seem to be a way to maintain the subscription status with those two applications.  Is there a way to isolate those two programs from Configurator control?  Better yet, is there a way to integrate them with Configurator without losing the subscription status and loss of huge amounts of data that are on a regular, FAA regulatory update schedule?  Configurator is awesome at managing iTunes managed applications and is perfect for our company.  I need to figure out how to make Configurator work with a subscription-based application.  Please help!

    Here is what is surmise reading ForeFlight web site.
    There is the app and the data.
    You manage the app through configurator or some other MDM.   The acquiring and paying for the data is independ of the configurator. You can buy the data through the app or online.  You may want to buy online. This way you can do the buying independent of the ipad. Once you have purchased, the app will download the data.  You may have to tell it to procedure with download panel.
    Some people use configurator to install mdm app then do the rest of the configuration from MDM.  This allows wifi updates of configuration.
    You end up with managing apps from MDM. You manage with your data from from the online account.  You enter appropriate password on each ipad to gain access to the data. App will download your data.  My need to tell it what to download in app.
    How do I buy a subscription?
    Purchasing a subscription is fast and easy! You can purchase a subscription online or inside the app using your iTunes account.
    To purchase a subscription inside the app, launch ForeFlight Mobile and then tap the 'Account' icon. You'll see a list of available plans to purchase in the 'Subscription Plans' table. Tap the one you want to buy. Follow the instructions for entering your email address and iTunes password. When the purchase is complete, you'll receive confirmation inside the app and immediately be able to continue using ForeFlight Mobile.
    To purchase a subscription online, visit our secure online ordering page. You'll be asked to choose a plan and enter your credit card information. After your purchase is complete, you'll receive an email with a password to sign into the app on your phone or iPad.
    http://www.foreflight.com/support/subscription#66
    How do I update charts, plates, and the airport database?
    ForeFlight Mobile has a download manager designed to make selecting, downloading, and updating your data easy- whether you like to store a little or a lot. Tap the Downloads icon from within the ForeFlight Mobile app. The Download Manager allows you to select the types of items you want to download and store on your device. ForeFlight Mobile will contact our servers and display the available updates. If you download updates that are not yet effective (future data sets) they will automatically be used by the software when they become effective. The download manager lets you pause a download and resume it later.
    http://www.foreflight.com/ipad/faqs/#11

  • ESS Bsns pkg  Bnfts &Pymnt - Overview Drop down and table not populated

    Hi All,
      We have configured ESS business package. Payslips in form of PDF are available in Benefits and payment.
    Overview dropdown and table are not getting populated.
    I checked context node rem, vcdata and attribute overview_sel in VcRem2Selection comp.
    They are not populated at any place as well. How does this work?
    Please guide
    Regards,
    Ganga

    Hi Gangadharayya,
    There are 2 ways of populating the dropdown.
    Either u can create a simple type and bind the attribute to the SimpleType, or use the class ISimpleTypeModifiable and IModifiableValueSet to populate the values at run-time.
    Hope this helps u
    Regards,
    Poojith M V

  • 1099 MISC configuration and processing

    Hello,
    Can someone please explain ( step by step) the configuration needed in order to:
    1) first set up vendors as a "1099 vendor:
    2) Configuration needed in order to create the electronic file to the IRS
    3) Any transactions, programs, and tables involved
    I don't need to know about the smart form or printing, as we have a company which does all that for us, but we have to provide the electrionic files.
    We are currently moving our system to a 6.0 platform, and the 1099 process is very customized in the old system, so i would like to understand all of the standard functionality 6.0 offers to generate this file...
    Thanks and will award points.
    Edited by: farmerj3 on Feb 8, 2011 2:50 PM

    Just checking one more time to see if anyone has any ideas. . . otherwise we may need to write a custom program to handle this.

  • Ask the Expert: Global Site Selector Configuration and Troubleshooting

    Welcome to this Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about configuring and troubleshooting the Global Site Selector (GSS) with expert Swati Chopra.
    GSS devices represent the next generation of application switches and global server load balancing (GSLB) appliances. Working together with the Cisco ACE Module and Cisco ACE 4710 appliance, these devices form an application-fluent networking solution that improves availability, acceleration, and security for data center applications.
    The primary role of Cisco GSS is to implement the business continuance and disaster recovery policies of a business by optimizing and securing the Domain Name System (DNS) infrastructure of the data center. It does this by integrating with the DNS infrastructure and responding to the client DNS requests, thereby directing the client to the site that is best able to serve its needs.
    Swati Chopra is a CCNA, CCNP, and VCP certified customer support engineer for content switching, covering technologies such as Cisco Application Control Engine, Cisco Wide Area Application Services, Global Site Selector, Cisco Content Services Switches, and Digital Media Suite. She has been with Cisco for more than three years and has worked with most of the high-end customers on content-related complex cases. She completed her master’s degree in finance, was heading an online education project in collaboration with e-Sylvan, and later moved to technical services because of her love for technology. She is actively involved with diverse Cisco initiatives such as Connected Women, WISE, and Cisco Career Connections and recently hosted a “Birds of Feather” table at Cisco’s Women of Impact conference.
    Remember to use the rating system to let Swati know if you have received an adequate response. 
    Because of the volume expected during this event, Swati might not be able to answer every question. Remember that you can continue the conversation in the Data Center community under subcommunity Application Networking shortly after the event. This event lasts through April 25, 2014. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

    Hi Sarah,
    The load balancing mechanism for GSS requests is done via different methods. We can use these methods to define how the load is shared for different balance clauses within the same rule. The 6 methods we use are:
    –round-robin—The GSS cycles through the list of answers that are available as requests are received. Each resource within an answer group is tried in turn. The GSS cycles through the list of answers, selecting the next answer in line for each request. This is the default.
    eg: if we have 2 answers in answer group then GSS will provide them alternatively.
    –least-loaded—The GSS selects an answer based on the load reported by each VIP in the answer group. The answer reporting the lightest load is chosen to respond to the request.The least-loaded option is available only for VIP-type answer groups that use a KAL-AP or Scripted keepalive, as they provide the GSS with detailed information on the SLB load and availability.
    eg: if one answer has higher load than the other, than first answer will not be provided until its load goes down the other answers
    –ordered—The GSS selects an answer from the list based on precedence; answers with a lower order number are tried first, while answers further down the list are tried only if preceding answers are unavailable to respond to the request.
    for eg: answer with ordered number 1 will be provided first till it becomes unavailable. Once it is unavailable then answer with ordered list number 2 will be provided
    –weighted-round-robin—The GSS cycles through the list of answers that are available as the requests are received, but sends requests to favored answers in a ratio determined by the weight value assigned to that resource.
    eg: if one answer has more weight(80%) than the other answer(20%), then it will be used 8 times out of 10.
    –hashed— When the GSS uses the hashed balance method, elements of the client's DNS proxy IP address and the requesting client's domain are extracted to create a unique value, referred to as a hash value. The unique hash value is attached to and used to identify a VIP that is chosen to serve the DNS query.
    The use of hash values makes it possible to "stick" traffic from a particular requesting client to a specific VIP, ensuring that future requests from that client are routed to the same VIP. This type of continuity can be used to facilitate features, such as online shopping baskets, in which client-specific data is expected to persist even when client connectivity to a site is terminated or interrupted.
    The GSS supports the following two hashed balance methods. You can apply one or both hashed balance methods to the specified answer group.
    • By Source Address—The GSS selects the answer based on a hash value created from the source address of the request.
    • By Domain Name—The GSS selects the answer based on a hash value created from the requested domain name.
    for eg: a user using same source ip will get the same answer from GSS if we do source address hashing.
    -DNS Race (Boomerang) Method-The GSS supports the DNS race (boomerang) method of proximity routing, which is a type of DNS resolution initiated by the GSS to load balance 2 to 20 sites.
    The boomerang method is based on the concept that instantaneous proximity can be determined if a CRA within each data center sends an A-record (IP address) at the exact same time to the client's D-proxy. The DNS race method of DNS resolution gives all CRAs (Cisco content engines or content services switches) a chance at resolving a client request and allows for proximity to be determined without probing the client's D-proxy. The first A-record received by the D-proxy is, by default, considered to be the most proximate.
    Use case is mainly with CRA's.
    Hope this helps. Please feel free to revert if you have follow-up questions.
    Thanks,
    Swati

  • Schema level and table level supplemental logging

    Hello,
    I'm setting up bi- directional DML replication between two oracle databases. I have enabled supplemental logging database level by running this command-
    SQL>alter database add supplemental log data (primary key) columns;
    Database altered.
    SQL> select SUPPLEMENTAL_LOG_DATA_MIN, SUPPLEMENTAL_LOG_DATA_PK, SUPPLEMENTAL_LOG_DATA_UI from v$database;
    SUPPLEME SUP SUP
    IMPLICIT YES NO
    -My question is should I enable supplemental logging table level also(for DML replication only)? should I run the below command also?
    GGSCI (db1) 1> DBLOGIN USERID ggs_admin, PASSWORD ggs_admin
    Successfully logged into database.
    GGSCI (db1) 2> ADD TRANDATA schema.<table-name>
    what is the deference between schema level and table level supplemental logging?

    For Oracle, ADD TRANDATA by default enables table-level supplemental logging. The supplemental log group includes one of the following sets of columns, in the listed order of priority, depending on what is defined on the table:
    1. Primary key
    2. First unique key alphanumerically with no virtual columns, no UDTs, no functionbased
    columns, and no nullable columns
    3. First unique key alphanumerically with no virtual columns, no UDTs, or no functionbased
    columns, but can include nullable columns
    4. If none of the preceding key types exist (even though there might be other types of keys
    defined on the table) Oracle GoldenGate constructs a pseudo key of all columns that
    the database allows to be used in a unique key, excluding virtual columns, UDTs,
    function-based columns, and any columns that are explicitly excluded from the Oracle
    GoldenGate configuration.
    The command issues an ALTER TABLE command with an ADD SUPPLEMENTAL LOG DATA clause that
    is appropriate for the type of unique constraint (or lack of one) that is defined for the table.
    When to use ADD TRANDATA for an Oracle source database
    Use ADD TRANDATA only if you are not using the Oracle GoldenGate DDL replication feature.
    If you are using the Oracle GoldenGate DDL replication feature, use the ADD SCHEMATRANDATA command to log the required supplemental data. It is possible to use ADD
    TRANDATA when DDL support is enabled, but only if you can guarantee one of the following:
    ● You can stop DML activity on any and all tables before users or applications perform DDL on them.
    ● You cannot stop DML activity before the DDL occurs, but you can guarantee that:
    ❍ There is no possibility that users or applications will issue DDL that adds new tables whose names satisfy an explicit or wildcarded specification in a TABLE or MAP
    statement.
    ❍ There is no possibility that users or applications will issue DDL that changes the key definitions of any tables that are already in the Oracle GoldenGate configuration.
    ADD SCHEMATRANDATA ensures replication continuity should DML ever occur on an object for which DDL has just been performed.
    You can use ADD TRANDATA even when using ADD SCHEMATRANDATA if you need to use the COLS option to log any non-key columns, such as those needed for FILTER statements and KEYCOLS clauses in the TABLE and MAP parameters.
    Additional requirements when using ADD TRANDATA
    Besides table-level logging, minimal supplemental logging must be enabled at the database level in order for Oracle GoldenGate to process updates to primary keys and
    chained rows. This must be done through the database interface, not through Oracle GoldenGate. You can enable minimal supplemental logging by issuing the following DDL
    statement:
    SQL> alter database add supplemental log data;
    To verify that supplemental logging is enabled at the database level, issue the following statement:
    SELECT SUPPLEMENTAL_LOG_DATA_MIN FROM V$DATABASE;
    The output of the query must be YES or IMPLICIT. LOG_DATA_MIN must be explicitly set, because it is not enabled automatically when other LOG_DATA options are set.
    If you required more details refer Oracle® GoldenGate Windows and UNIX Reference Guide 11g Release 2 (11.2.1.0.0)

  • Help - option premium calculator configuration and testing

    Hi Experts,
    I've been reading up on Option premium calculator in saphelp.com but it doesn't give me pre-requisites that are to be maintained first before TXAK can be used perfectly.
    Would like to request for assistance in 1) customizing/configuring and 2) testing the Option premium calculator..
    Customizing done so far (using DUMMY Values):
    A) Yield Curve type 9999, Curr SGD maintenance in table JBD14
    B) Reference Interest rate for yield curve 9999 via txn JBYC
    customizing via SPRO (using DUMMY values):
    C) Define reference interest rate (NOMVAL_SGD)
    FSCM > TRM > Basic functions > Market data mgmt > Master data > settings for ref. interest rates and yield curves for analyzersMaintain Exchange rate volatilities
    D) Enter exchange rate volatilities for transaction currencies
    FSCM > TRM > Basic Functions > Market data mgmt > Manual market data entry > Statistical data > Enter exchange rate volatilities
    Please do let me know what other data I SHOULD MAINTAIN aside from the items above..
    Thanks!
    David

    Hi David,
    strange, it says you posted it last year, but I haven't seen your thread before.
    For testing, see links: http://help.sap.com/erp2005_ehp_04/helpdata/EN/d2/6f7cb2415e11d182b10000e829fbfe/frameset.htm
    http://help.sap.com/erp2005_ehp_04/helpdata/EN/d2/6f7cb2415e11d182b10000e829fbfe/frameset.htm.
    But I suppose you already got some answers in your other post:
    Re: Option premium calculation for OTC Currency options
    BR, Tomislav

  • Relationship b/w sga configuration and boot.ini in windows platforms

    hi all,
    i have doubt on sga configuration and boot.ini settings.
    assume the following configuration's
    1.Db is 10g r2.
    2.OS is Windows server 2003 ,RAM is 8gb
    3.SGA_max_size=4gb,SGA_atrget=4gb
    1.For the above settings i must initialize the /3g /PAE in bott.ini file?
    2. the boot.ini configuration is optional one?
    3. what is criteria to set the /3g /PAE parameter in boot.ini and why?
    4. what is advantage and disadvantage of boot.ini
    please explain.
    Thanks is advance..

    Deepak_DBA wrote:
    hi,
    1.Db is 10g r2.
    2.OS is Windows server 2003 ,RAM is 8gb
    3.SGA_max_size=4gb,SGA_atrget=4gbfor this configuration no need to set /3g /PAE..
    coz in Windows server 2003
    When the physical RAM in the system exceeds 16 GB and the /3GB switch is used, the operating system will ignore the additional RAM until the /3GB switch is removed. This is because of the increased size of the kernel required to support more Page Table Entries. The assumption is made that the administrator would rather not lose the /3GB functionality silently and automatically; therefore, this requires the administrator to explicitly change this setting.
    The /3GB switch allocates 3 GB of virtual address space to an application that uses IMAGE_FILE_LARGE_ADDRESS_AWARE in the process header. This switch allows applications to address 1 GB of additional virtual address space above 2 GB.
    The virtual address space of processes and applications is still limited to 2 GB, unless the /3GB switch is used in the Boot.ini file. The following example shows how to add the /3GB parameter in the Boot.ini file to enable application memory tuning:
    [boot loader]
    timeout=30
    default=multi(0)disk(0)rdisk(0)partition(2)\WINNT
    [operating systems]
    multi(0)disk(0)rdisk(0)partition(2)\WINNT="????" /3GB
    so no need to se the bbot.ini files in your case..
    Deepak,
    Its not good to quote from a link and not give the entire link.
    http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx
    HTH
    Aman....

  • Is XS Project right for Database Schema and tables

    Hi Friends
    1.As per OpenSAP video it is suggesting to use XS Project for Database objects.
    In my case I am planning to do AO Reporting and not creating any UI , is XS project still the right project type.
    There is an option for General ->Project - would that be the right one.
    2. Also in my UI I am not able to see the Prefrences->SAP Hana Development ->Repository Access to set the regit.exe. I did see couple of post mentioned about it but the response was not very clear , hence asking the question again.
    regards
    Poonam

    Hi Poonam,
    Poonam Hemrajani wrote:
    1.As per OpenSAP video it is suggesting to use XS Project for Database objects.
    In my case I am planning to do AO Reporting and not creating any UI , is XS project still the right project type.
    There is an option for General ->Project - would that be the right one.
    Project is used to group all the required development artifacts and the libraries required for them. So based on your requirement you can choose. I think "General" project would suffice your requirement if it is only to create schemas and tables.
    But on the other hand if you choose to build an application using XS related libraries you can either choose to import those libraries later or create using a XS project now.
    Will wait along with you to see  Thomas Jung comments on this.
    Poonam Hemrajani wrote:
    2. Also in my UI I am not able to see the Prefrences->SAP Hana Development ->Repository Access to set the regit.exe. I did see couple of post mentioned about it but the response was not very clear , hence asking the question again.
    Firstly from SP7, it is not required to setup regi.exe file. This file resides in hdbclient folder. So you need to check where you have installed hdbclient to see if you have that regi.exe file and configure it accordingly in the Path ( Preferences --> SAP HANA Development --> Repository Access ) you mentioned.
    Regards,
    Krishna Tangudu

  • Idoc Configuration and interfaces related to 810

    Hi,
      Can any one tell me the entire configuration of ALE and EDI810 supported tools?
    Thanks
    Shobi

    <b>Hi,
    ALE
    To develop a new custom ALE scenario, comprises 5 steps:
    1.     Design and develop the custom IDoc with it’s segments and a new message type
    2.     Configure the ALE environment with the new IDoc and message type (customer model, partner profiles and linking IDoc to message type)
    3.     Develop the outbound process which does the following:
    •     Populates the custom IDoc with control info and functional data
    •     Sends the IDoc to the ALE layer for distribution
    •     Updates status and handles errors
    4.     Configure the ALE inbound side (partner profiles with inbound process code)
    5.     Develop the inbound process which does the following:
    •     Reads the IDoc into a BDC table; selects other data that is required
    •     Runs transaction using call transaction or BDC session
    •     Updates status and handles errors
    Below is a pictorial representation of the flow of a complete ALE scenario from the sending system to the receiving system.
    Figure 1: ALE Scenario model
    1.1.     ALE Example
    For the purposes of this example we will develop a small ALE scenario. This scenario is described below.
    “The receiver of an internal service must be able to reverse (cancel) the invoice receipt which will then cancel the applicable billing document automatically on the service provider’s system.”
    Figure 2: Example Purchasing & Selling scenario
    We will develop a custom IDoc to carry the billing number from the Service Receiver’s system to the Service Provider’s system. We will populate the IDoc in a user exit on the sending side and we will process the transaction on the receiving side using a custom function module and a BDC transaction call.
    No rule conversion, segment filtering or version conversion will be implemented in the model as described in Figure 1.
    Requirements
    •     Working ALE environment - See ALE Basis Configuration Guide;
    •     ALE scenario design together with the business requirement;
    •     Development access; and
    •     ALE configuration access.
    NOTES:
    1.     All IMG references to transactions are located in the transaction SALE which is the ALE portion of the IMG
    2.     This is one way of developing a scenario where no message control exists. If message control exist (EG. On purchase orders) then NAST can be used to call an outbound function module that would create the required IDocs.
    3.     Extensive knowledge of IDocs and ALE basis configuration is required in order to understand this guide.
    2.     OUTBOUND PROCESSING
    2.1.     Create IDoc type (WE30) Client independent
    The IDoc type refers to the IDoc structure that you will require for your development. In our case the IDoc type is called ZINVRV01. This IDoc type will have 1 segment called Z1INVRV with 2 fields, LIFNR & XBLNR, in this segment. If you require many segments or nested segments then they are also created using the same procedure.
    We will create the IDoc of the following structure:
    ZINVRV01
    Purchasing and Selling - Invoice receipt reversal
    Z1INVRV     P&S - Segment 1
         Segment fields     
              LIFNR     Vendor account number
              XBLNR     Reference document number
    Figure 3: IDoc type ZINVRV01
    To create the IDoc type, follow these next few steps:
    •     Enter transaction WE30 (ALE -> Extensions -> IDoc types -> Maintain IDoc type)
    •     Type in ZINVRV01 and click on Basic IDoc type, click the Create icon
    •     Click on Create new (we are creating an IDoc from scratch but you may want to copy another IDoc if it is similar to your requirements) and enter a description, and press enter
    •     Click on ZINVRV01 and then on the Create icon
    •     Enter Z1INVRV as the segment type (must start with Z1), check mandatory if the segment must exist (in this case check it), enter 1 in minimum number and 1 as maximum number. (Make the maximum number 9999999999 if there are going to be many of these segments in each IDoc. IE. When line items are passed via IDocs), click on Segment editor
    •     Enter a description for your segment type and create
    •     Enter a description for your segment, enter each field required in your IDoc, in our case type LIFNR across for Field name, DE structure and DE documentation, repeat for XBLNR and press enter to validate.
    •     Save and generate, press back
    •     To release the segment choose Goto, Release from the menu
    •     Check the box on the line of your new segment
    •     Save, back and enter
    •     Your IDoc type structure should be displayed with your new segment
    •     Save and back
    •     To release the IDoc type choose Extras, Release type from the menu and Yes
    Your IDoc is now ready for use. If you need to add fields or segments to your IDoc type, you will need to cancel the release of the IDoc type as well as the segment release using a similar procedure followed above (except now you uncheck the release box for the segment and you choose cancel release for the IDoc type).
    2.2.     Create message type (WE81) Client independent
    To create a new message type, follow these next few steps:
    •     Enter transaction WE81 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Create logical message type)
    •     Choose Create logical message type by double clicking on it
    •     Click on change icon to enter change mode
    •     Click on New entries to add a new type
    •     Enter the required message type, in our case it is ZINVRV and an appropriate description
    •     Save and exit.
    Your message type has now been created. The next step will be to link it to the IDoc.
    2.2.1.     Link message to IDoc type (WE82 & BD69) Client independent
    To link the message type to the IDoc type follow these next few steps:
    •     Enter transaction WE82 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> EDI: Message Types and Assignment to IDoc Types)
    •     Click on change icon to enter change mode
    •     Click on New entries to create the link
    •     Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
    •     Save and exit
    •     Enter transaction BD69 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Assign message type to IDoc for ALE)
    •     Click on change icon to enter change mode
    •     Click on New entries to create the link
    •     Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
    •     Save and exit
    Your IDoc is now linked to your message type. We still need to link object types and add the message to the model before we can use the message.
    2.2.2.     Maintain object type for message type (BD59) Client independent
    The ALE objects are used to create links between IDocs and applications objects, to control the serialisation, to filter messages in the customer model and to use listings.
    For our own message type and IDoc you must maintain object types for the links.
    If you want to check the serialisation for the message type, then you must maintain object types for the serialisation. If no serialisation object has been maintained for a given message type, then the serialisation will not be checked for this message type.
    To add an object type to our message type, follow these next few steps:
    •     Enter transaction BD59 (ALE -> Extensions -> ALE object maintenance -> Maintain object types)
    •     Type in your message type ZINVRV and press enter
    •     Click on New entries
    •     Enter your object type, LIFNR (We need to use the vendor as a filter object), the segment name where LIFNR resides, Z1INVRV, a number 1 for the sequence followed by the actual field name LIFNR
    •     Save and exit.
    You have now created an object that we’ll use as a filter object in the customer model to direct the flow of messages to the various logical systems based on the vendors in the filter of the message type ZINVRV.
    We now need to add our new message type to the distribution model.
    2.3.     Configuring the Distribution Model
    This task is performed on your ALE reference client.
    2.3.1.     Manual Configuration (BD64) Client dependent
    To manually configure the customer distribution model, read the ALE configuration procedure, and follow these steps:
    •     Perform the Maintain customer distribution model directly function. (ALE -> Distribution customer model -> Maintain customer distribution model directly)
    •     Specify the customer model you want to maintain and the logical system that is to be the sender of the messages OR create a new model. (Create model ALE with logical system ALELS1C400)
    •     Choose the receiving systems to which the sending system must forward message type ZINVRV to.
    •     For each receiving logical system allocate the message type necessary for communication to the receiving systems as per ALE configuration procedure.
    •     Create filter objects (in our case LIFNR as the object type with the associated vendor number, 0000018001 with leading zeros, in the object area) for the message types.
    •     Save the entries.
    NOTES:
    You cannot maintain a message type between the same sender and receiver in more than one customer distribution model.
    Only the owner is authorised to modify the model.
    To change the owner of a model, choose the 'Maintain ownership of customer distribution model' function. Make sure that all changes will be distributed to all systems that know the corresponding model. To do so, you can use the correction and transport system.
    To transport the customer distribution model you should use the Distribute customer model function of the IMG as described below.
    2.3.2.     Distribute customer model (BD71) Client dependent
    After the customer model has been created centrally, it must be distributed to the other remote systems. This entails first of all setting up the communication for the distributed systems and then sending the model.
    2.3.2.1.     Distribute Model (BD71) Client dependent
    This task is performed on your ALE reference client. To distribute the customer distribution model, read the ALE configuration procedure and follow these steps:
    •     Make the settings for the communication with the other decentral systems, you have not set them yet.
    •     Define the RFC destination for R/3 connections whose names correspond to the name of the corresponding logical system.
    •     Create the output partner profile.
    •     Distribute the customer model
    •     Specify the name of the customer model.
    •     You must specify the target system to which you want to distribute the customer model.
    •     You must repeat this function for every distributed logical system.
    2.3.2.2.     Maintain sending system partner profile (WE20) Client dependent
    With this function, you define the partner profiles for all outbound and inbound messages on the basis of the customer distribution model.
    After you have defined and distributed the customer model, you will have to maintain the partner profiles locally. To do this read the ALE configuration procedure.
    •     Enter the output mode (background, immediately) and the package size for outbound processing.
    Requirements
    •     The customer model must be maintained.
    •     RFC destinations must be maintained.
    •     The customer model must be distributed.
    •     To ensure that the appropriate persons in charge are informed if a processing error occurs, you must make settings in: Error processing Maintain organisational units.
    2.4.     Populate & distribute IDoc using ABAP
    An IDoc consists of a control record with structure edidc and one or more data records with structure edidd. The control record contains the sender and recipient of the IDoc, as well as information on the type of message.
    To be able to pass an IDoc to the ALE layer, you must set up a field string with structure edidc and an internal table with structure edidd. They are used to call function module master_idoc_distribute, which performs the save to the database and triggers the dispatch if necessary.
    2.4.1.     Example code
    The code displayed below does the following:
    •     populates our IDoc segment Z1INVR with the 2 fields XBLNR and LIFNR, populates the segment name and appends this to an internal table used to store the IDoc data;
    •     populates the control record info with the message type and IDoc type; and
    •     calls the MASTER_IDOC_DISTRIBUTE function module which distributes the IDoc as configured in the customer distribution model.
    *--- Data declaration statements
    DATA:          C_INVREV_SEGNAME(7) TYPE C VALUE 'Z1INVRV',
              C_INVREV_MESTYPE(6) TYPE C VALUE 'ZINVRV',
              C_INVREV_IDOC_TYPE(8) TYPE C VALUE 'ZINVRV01',
              Z1INVRV LIKE Z1INVRV,
              C_INVREV_DOCTYPE LIKE BKPF-BLART VALUE 'YY',
              IDOC_CONTROL LIKE EDIDC,
              T_COMM_CONTROL LIKE EDIDC OCCURS 0 WITH HEADER LINE,
              IDOC_DATA LIKE EDIDD OCCURS 0 WITH HEADER LINE.
    *--- Move the document header into a structure
    LOOP AT DOC_HEAD_TAB INTO DOC_HEAD.
    ENDLOOP.
    *--- Move the document item data into a structure
    LOOP AT DOC_ITEM_TAB INTO DOC_ITEM WHERE NOT ( LIFNR IS INITIAL ).
    ENDLOOP.
    *--- Populate the IDoc segment’s field with the required data
    CLEAR Z1INVRV.
    Z1INVRV-LIFNR = DOC_ITEM-LIFNR.          “Store vendor number for filter
    Z1INVRV-XBLNR = DOC_HEAD-XBLNR.          “Billing number
    IDOC_DATA-SEGNAM = C_INVREV_SEGNAME.     “Segment name
    IDOC_DATA-SDATA = Z1INVRV.               “Segment data
    APPEND IDOC_DATA.                    “Populate IDoc internal table
    *--- Move the control data info required for the distribution
    IDOC_CONTROL-MESTYP = C_INVREV_MESTYPE.
    IDOC_CONTROL-DOCTYP = C_INVREV_IDOC_TYPE.
    *--- Call the distribute function with the required parameters
    CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE' IN UPDATE TASK
              EXPORTING
                   MASTER_IDOC_CONTROL          = IDOC_CONTROL
              TABLES
                   COMMUNICATION_IDOC_CONTROL     = T_COMM_CONTROL
                   MASTER_IDOC_DATA               = IDOC_DATA
              EXCEPTIONS
                   ERROR_IN_IDOC_CONTROL               = 1
                   ERROR_WRITING_IDOC_STATUS          = 2
                   ERROR_IN_IDOC_DATA               = 3
                   SENDING_LOGICAL_SYSTEM_UNKNOWN      = 4
                   OTHERS                         = 5.
    Figure 4: Outbound processing example code
    NOTE:
    For debugging purposes, use transaction WE05 (IDoc overview) to see check your IDoc status, or to see whether an IDoc was created/
    3.     INBOUND PROCESSING
    3.1.     Create Function Module
    This function module is called when a message type, of type ZINVRV, comes into the receiving system. This needs to be configured and is dealt with later in this section. The function module is passed the IDoc as a parameter.
    Example parameters
    Import parameters     Reference field     Opt Y/N
    INPUT_METHOD     BDWFAP_PAR-INPUTMETHD     N
    MASS_PROCESSING     BDWFAP_PAR-MASS_PROC     N
    Export Parameters     Reference field     Opt Y/N
    WORKFLOW_RESULT     BDWFAP_PAR-RESULT     N
    APPLICATION_VARIABLE     BDWFAP_PAR-APPL_VAR     N
    IN_UPDATE_TASK     BDWFAP_PAR-UPDATETASK     N
    CALL_TRANSACTION_DONE     BDWFAP_PAR-CALLTRANS     N
    Table Parameters     Reference field     Optional Y/N
    IDOC_CONTRL     EDIDC     
    IDOC_DATA          EDIDD     
    IDOC_STATUS     BDIDOCSTAT     
    RETURN_VARIABLES     BDWFRETVAR     
    SERIALIZATION_INFO     BDI_SER     
    Exceptions
    WRONG_FUNCTION_CALLED
    Example code
    The code displayed below does the following:
    •     populates a BDC table with the IDoc info;
    •     calls the transaction via a BDC call; and
    •     updates the IDoc status according to the BDC error status.
    EXTRACT FROM: Z_IDOC_INPUT_ZINVRV
    *--- Declaration of local variables
    DATA: C_SEGNAM(10) TYPE C VALUE 'Z1INVRV'.
    *-Loop through the IDOCs
    LOOP AT IDOC_CONTRL.
    *---Loop through the data for the IDOC
         LOOP AT IDOC_DATA WHERE DOCNUM = IDOC_CONTRL-DOCNUM.
              CASE IDOC_DATA-SEGNAM.
                   WHEN C_SEGNAM.
    *                    Here we get the info from the idoc table
                        IT_Z1INVRV = IDOC_DATA-SDATA.
              ENDCASE.
              PERFORM REV_INV.
         ENDLOOP.
         PERFORM UPDATE_IDOC_STATUS.
    ENDLOOP.
    FORM REV_INV               "Reverse invoice form
    *--- Local variables & constants
    DATA: C_TCODE LIKE BKPF-TCODE VALUE 'VF11'.  "BDC transaction code
    *--- Now we can build the bdc table to call the reversal transaction start of screen 109
    CLEAR BDC_TAB.
    BDC_TAB-PROGRAM  = 'SAPMV60A'.
    BDC_TAB-DYNPRO   = '109'.
    BDC_TAB-DYNBEGIN = 'X'.
    APPEND BDC_TAB.
    *--- Document number
    CLEAR BDC_TAB.
    BDC_TAB-FNAM = 'KOMFK-VBELN(01)'.
    BDC_TAB-FVAL = IT_Z1INVRV-XBLNR.     "Billing document number
    APPEND BDC_TAB.
    *--- OK Code for screen 109
    CLEAR BDC_TAB.
    BDC_TAB-FNAM = 'BDC_OKCODE'.
    BDC_TAB-FVAL = 'SICH'.
    APPEND BDC_TAB.
    *--- Now we can call transaction 'VF11' with the populated bdc table. The transaction is called inside the idoc-contrl loop, so a transaction will be called for every idoc (journal). the transaction is called in no-display mode ('N') because this code runs in background as it is called by ale.  The update is specified to be synchronous ('S') because we have to wait for the result to update the idoc status correctly.
    CALL TRANSACTION C_TCODE USING BDC_TAB MODE 'N' UPDATE 'S'.
    *--- Store the return code for use in another form (status update)
    RETURN_CODE = SY-SUBRC.
    *--- Here we check the return code, if there was an error, we put the transaction in a bdc session for the user to review and correct.
    IF SY-SUBRC NE 0.
         CALL FUNCTION 'BDC_OPEN_GROUP'
              EXPORTING
                   CLIENT = SY-MANDT
                   GROUP  = 'ZINVRV'
                   USER   = C_ALE_USER
                   KEEP   = 'X'.
         CALL FUNCTION 'BDC_INSERT'
              EXPORTING
                   TCODE     = C_TCODE
              TABLES
                   DYNPROTAB = BDC_TAB.
         CALL FUNCTION 'BDC_CLOSE_GROUP'
              EXCEPTIONS
                   NOT_OPEN    = 1
                   QUEUE_ERROR = 2
                   OTHERS      = 3.
    ELSE.                              "No problems
         C_EXISTS = 'N'.
      Select from the billing document table to get sales doc number
         SELECT * FROM VBRP WHERE VBELN = IT_Z1INVRV-XBLNR.
        Select from the sales document table to get user status number
              SELECT SINGLE * FROM VBAP WHERE VBELN = VBRP-AUBEL AND
                   POSNR = VBRP-AUPOS.
        Select from the status table to change the user status to pending
              SELECT * FROM JEST WHERE OBJNR = VBAP-OBJNR AND
                   STAT LIKE C_USER_STATUS.
                   IF JEST-STAT = C_US_PENDING.   "User status is pending
                        JEST-INACT = C_UNCHECKED.    "Make pending the active status
                        UPDATE JEST.
                        C_EXISTS = 'Y'.            "I.E. An entry is already in table
                   ELSEIF JEST-INACT = C_UNCHECKED AND JEST-STAT NE C_US_PENDING.
                        JEST-INACT = C_CHECKED.      "Make everything else inactive
                        UPDATE JEST.
                   ENDIF.
              ENDSELECT.
              IF C_EXISTS = 'N'.    "I.E. Pending has never been a status before
                   JEST-OBJNR = VBAP-OBJNR.
                   JEST-STAT  = C_US_PENDING.
                   JEST-INACT = C_UNCHECKED.      "Make pending the active status
                   INSERT JEST.
              ENDIF.
         ENDSELECT.       "Select from VBRP (Billing document table)
    ENDIF.
    ENDFORM.                               " REV_INV
    FORM UPDATE_IDOC_STATUS.                                              
    *--- Now we check the CALL TRANSACTION return code and set IDOC status
         CLEAR IDOC_STATUS.                                                  
         IF RETURN_CODE = 0.                                                 
              WORKFLOW_RESULT = '0'.                                            
              IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.                          
              IDOC_STATUS-STATUS = '53'.                                        
              IDOC_STATUS-UNAME = SY-UNAME.                                     
              IDOC_STATUS-REPID = SY-REPID.                                     
              IDOC_STATUS-MSGTY = SY-MSGTY.                                     
              IDOC_STATUS-MSGID = SY-MSGID.                                     
              IDOC_STATUS-MSGNO = SY-MSGNO.                                     
              IDOC_STATUS-MSGV1 = SY-MSGV1.                                     
              IDOC_STATUS-MSGV2 = SY-MSGV2.
              IDOC_STATUS-MSGV3 = SY-MSGV3.                        
              IDOC_STATUS-MSGV4 = SY-MSGV4.                        
              RETURN_VARIABLES-WF_PARAM = 'Processed_IDOCs'.       
              RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.    
              APPEND RETURN_VARIABLES.                             
         ELSE.                                                  
              WORKFLOW_RESULT = '99999'.                           
              IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.             
              IDOC_STATUS-STATUS = '51'.                           
              IDOC_STATUS-UNAME = SY-UNAME.                        
              IDOC_STATUS-REPID = SY-REPID.                        
              IDOC_STATUS-MSGTY = SY-MSGTY.                        
              IDOC_STATUS-MSGID = SY-MSGID.                        
              IDOC_STATUS-MSGNO = SY-MSGNO.                        
              IDOC_STATUS-MSGV1 = SY-MSGV1.
              IDOC_STATUS-MSGV2 = SY-MSGV2.                         
              IDOC_STATUS-MSGV3 = SY-MSGV3.                         
              IDOC_STATUS-MSGV4 = SY-MSGV4.                         
              RETURN_VARIABLES-WF_PARAM = 'ERROR_IDOCS'.            
              RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.     
              APPEND RETURN_VARIABLES.                              
         ENDIF.                                                  
         APPEND IDOC_STATUS.                                     
    ENDFORM.                               " UPDATE_IDOC_STATUS
    Figure 5: Inbound processing example code
    3.1.1.     Debugging inbound FM
    Use transaction WE19 to test inbound function module in debugging mode. Also use WE05 to view the IDocs and their statuses.
    3.2.     Maintain ALE attributes
    The inbound function module needs to be linked to the message type and the message type needs to be linked to the appropriate inbound process code at the partner profile level before the scenario is enabled. These steps are described below in detail.
    3.2.1.     Link Message Type to Function Module (WE57) Client independent
    To link a message (ZINVRV) type to a function module (Z_IDOC_INPUT_ZINVRV) follow these steps:
    •     Enter transaction WE57 (ALE -> Extensions -> Inbound -> Allocate function module to logical message)
    •     Select an entry (EG. IDOC_INPUT_ORDERS) and copy
    •     Type in module name Z_IDOC_INPUT_ZINVRV
    •     Type in basic IDoc type as ZINVRV01
    •     Type in message type as ZINVRV
    •     Type object type as IDOCINVOIC (Invoice document) - Used for workflow
    •     Direction should be set to 2 for inbound
    •     Enter and save
    3.2.2.     Define FM settings (BD51) Client independent
    •     Enter transaction BD51 (ALE -> Extensions -> Inbound -> Define settings for input modules)
    •     Click on New entries
    •     Type in the name of the new function module Z_IDOC_INPUT_ZINVRV
    •     Enter 0 for mass processing in the output column
    •     Save and Exit
    3.2.3.     Maintain process codes (WE42) Client dependent
    A process code needs to be maintained on each client. It then needs to be linked to the message via the partner profiles on each client. This allows the various clients to use a unique function module for the same message type.
    To maintain the process code follow these steps:
    •     Log on to the appropriate receiving system client
    •     Execute WE42 (ALE -> Extensions -> Inbound -> Maintaining process codes inbound)
    •     Choose Inbound with ALE service
    •     Choose Processing with function module
    •     Click on Processing with function module and choose create icon
    •     Click on New Entries
    •     Type in process code ZINR and give it a description and save
    •     Now you are asked to Please maintain codes added in ALE entry methods, enter and choose Z_IDOC_INPUT_FIRVSL and copy it. You should choose a FM similar to your one.
    •     Enter your process code ZINR
    •     Enter your function module Z_IDOC_INPUT_ZINVRV
    NOTE: The next 6 steps are used in workflow error handling.
    •     Enter IDPKFIDCMT in object type
    •     Enter MASSINPUTFINISHED in End event
    •     Enter IDOCINVOIC in IDoc object type
    •     Enter INPUTERROROCCURREDFI in IDoc start event
    •     Enter INPUTFINISHEDFI in IDoc End event
    •     Enter IDOCINVOIC in Application object type
    You will need to determine the task associated with object IDOCINVOIC, and then assign the appropriate position to it. This position will then receive the application error messages via workflow.
    To set up the workflow area please consult the Workflow config guide.
    3.3.     Create inbound partner profile
    For each message type you need to maintain the inbound partner profiles.
    3.3.1.     Maintain receiving system partner profile (WE20) Client dependent
    To maintain inbound partner profiles read the document ALE configuration procedure:
    •     Add the message type ZINVRV with process code ZINR.
    •     Enter the output mode (background, immediately) for inbound processing and NO message code.
    •     Enter the position S and choose the ALE administrator 50000085. This position will then receive all the technical ALE errors via workflow.
    3.4.     Test
    Once the inbound function module has been debugged the scenario should be ready to test in its entirety. If problems occur, read through the relevant areas of this document to check your configuration or code.</b>
      Foe EDI 810 Mapping Refer  <b>http://www.altova.com/videos.asp?type=0&video=edimapping</b>.
    Online demo you can see,
    Thanks
    Manju

  • Two Questions Re: Embedding Flash and Tables Shortcut

    .
    Two Questions Re: Embedding Flash and Tables Shortcut
    1) I work on a Mac and use Dreamweaver 8. Often I like to
    embed Flash objects into a page and I do this by using
    Dreamweaver's INSERT > MEDIA > FLASH. However, the SWF file
    doesn't show up on the published web page and I’ve never had
    this issue using previous versions, so I’m not sure what to
    do? Here's what Dreamweaver generates when I use their INSERT
    feature:
    <script type="text/javascript">
    AC_FL_RunContent( 'codebase','
    http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=7,0,19,0','wid th','550','height','180','src','flash/BANNER.HOME','quality','high','pluginspage','http:// www.macromedia.com/go/getflashplayer','movie','flash/BANNER.HOME'
    ); //end AC code
    </script><noscript><object
    classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" codebase="
    http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=7,0,19,0"
    width="550" height="180">
    <param name="movie" value="flash/BANNER.HOME.swf">
    <param name="quality" value="high">
    <embed src="flash/BANNER.HOME.swf" quality="high"
    pluginspage="
    http://www.macromedia.com/go/getflashplayer"
    type="application/x-shockwave-flash" width="550"
    height="180"></embed>
    It seems a bit weird that the SWF file is not showing
    considering Flash & Dreamweaver are the most compatible apps,
    no? I’m assuming if Dreamweaver is generating this code it
    should work, no?
    2) I’m getting an error when trying to use the Tables
    short cut COMMAND+ OPTION+T that reads...
    "While executing objectTag, the following JavaScript error(s)
    occurred:
    At line 26 of file “Macintosh
    HD:Applications:Macromedia Dreamweaver 8:
    Configuration:Objects:Common:Table.htm”:
    TypeError: cmdDOM.parentWindo.createTableStr is not a
    function"
    What’s strange is it was working fine last week and for
    the life of me I don’t know what could of happened to make
    this shortcut get corrupted?
    I’ve reinstalled the app multiple times and still I get
    the same error :-(
    Any help is greatly appreciated!
    Thanks in advance!
    .

    > It seems a bit weird that the SWF file is not showing
    considering Flash &
    > Dreamweaver are the most compatible apps, no? I?m
    assuming if
    > Dreamweaver is
    > generating this code it should work, no?
    It works. Most likely you have not uploaded the Scripts
    folder referenced
    in the head of the page.
    > What?s strange is it was working fine last week and for
    the life of me I
    > don?t
    > know what could of happened to make this shortcut get
    corrupted?
    Troubleshooting JavaScript errors in Dreamweaver
    http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=tn_19105#dat
    Murray --- ICQ 71997575
    Adobe Community Expert
    (If you *MUST* email me, don't LAUGH when you do so!)
    ==================
    http://www.dreamweavermx-templates.com
    - Template Triage!
    http://www.projectseven.com/go
    - DW FAQs, Tutorials & Resources
    http://www.dwfaq.com - DW FAQs,
    Tutorials & Resources
    http://www.macromedia.com/support/search/
    - Macromedia (MM) Technotes
    ==================
    "Rupda" <[email protected]> wrote in message
    news:[email protected]...
    > .
    >
    >
    Two Questions Re: Embedding Flash and Tables Shortcut
    >
    >
    >
    1) I work on a Mac and use Dreamweaver 8. Often I like to
    embed
    > Flash
    > objects into a page and I do this by using Dreamweaver's
    INSERT > MEDIA >
    > FLASH. However, the SWF file doesn't show up on the
    published web page
    > and
    > I?ve never had this issue using previous versions, so
    I?m not sure what to
    > do?
    > Here's what Dreamweaver generates when I use their
    INSERT feature:
    >
    >
    <script type="text/javascript">
    > AC_FL_RunContent(
    > 'codebase','
    http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#
    >
    version=7,0,19,0','width','550','height','180','src','flash/BANNER.HOME','qualit
    > y','high','pluginspage','
    http://www.macromedia.com/go/getflashplayer','movie','f
    > lash/BANNER.HOME' ); //end AC code
    > </script><noscript><object
    > classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000"
    > codebase="
    http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#ve
    > rsion=7,0,19,0" width="550" height="180">
    > <param name="movie" value="flash/BANNER.HOME.swf">
    > <param name="quality" value="high">
    > <embed src="flash/BANNER.HOME.swf" quality="high"
    > pluginspage="
    http://www.macromedia.com/go/getflashplayer"
    > type="application/x-shockwave-flash" width="550"
    height="180"></embed>
    >
    >
    > It seems a bit weird that the SWF file is not showing
    considering Flash &
    > Dreamweaver are the most compatible apps, no? I?m
    assuming if
    > Dreamweaver is
    > generating this code it should work, no?
    >
    >
    >
    >
    2) I?m getting an error when trying to use the Tables short
    cut
    > COMMAND+ OPTION+T that reads...
    >
    >
    "While executing objectTag, the following JavaScript error(s)
    occurred:
    > At line 26 of file ?Macintosh HD:Applications:Macromedia
    Dreamweaver 8:
    > Configuration:Objects:Common:Table.htm?:
    > TypeError: cmdDOM.parentWindo.createTableStr is not a
    function"
    >
    >
    > What?s strange is it was working fine last week and for
    the life of me I
    > don?t
    > know what could of happened to make this shortcut get
    corrupted?
    >
    > I?ve reinstalled the app multiple times and still I get
    the same error
    > :-(
    >
    >
    >
    > Any help is greatly appreciated!
    >
    >
    > Thanks in advance!
    >
    > :-)
    >
    > .
    >

  • Internal error in communication between configuration and sales document

    Hi,
    While i am doing VA32 i got this message  plz advise me..
    Internal error in communication between configuration and sales document
    in the form GET_CONFIG_MODE
    bit urgent  issue..
    Regards,
    San Rao.

    Hi
    Pls check the OSS note 836097, which can solve your problem.
    In my experience, I can tell you something
    When configuration is done, the configuration object is stored in VBAP-CUOBJ for the item. For this CUOBJ, you can find the configuration in the tcode CUTABLEINFO or in tables IBIB, IBIN, IBEXTINST, IBINOBS,IBINOWN,IBST,IBSTREF,IBINVALUES.
    If for the order if VBAP-CUOBJ is not available, then it will not be able to get the configuration. The error message in this case is V1 854 of message class V1.
    You can search for some other OSS notes also using this error message and the form name.
    Also refer to 173726, 174333,175372 and 173664

  • How to make two matrix and table into same group in SSRS

    Hi
    i need to dispaly to dispaly data  matrix and table .  but matrix data on first page and table data on second page.
    how to achive this . if i give pagebreak for every new instance for matrix, only matrix data is getting dispalyed in one page and on the second page seocond record date is getting displayed. after all matrix data is displayed ( in separate pages) , table
     data is being dispalyed.
    but i want to display matrix data on first page and table data on the second page for the first record. for second record  also it should display matrix data on 3rd page and table data on 4th page etc..
    i mean how to make matrix and table data as same group. so that i can set "page break for new instamce" etc..
    how to achive this in SSRS2008

    Hi Ramkanuganti,
    From your description, you want to group both the matrix and table on the same field and add a page break between the two controls for each instance at run time.
    To achieve your goal, we can display the matrix in a list and display the table in a nesting list. Please refer to the steps below:
    Drag a “List” to the design surface. Drag the matrix into the top of the list (list1).
    Drag a “”List” to the list1, under the matrix. Drag the table into the nesting list (list2).
    Select “list1” and open the “Group Properties” from the “Row Groups” pane. Add the field on which you want to group the data. In the “Page Breaks” tab, select the “Between each instance of a group”.
    Repeat step 3 to configure the “list2” using the same field. Additionally, please also select the “Also at the start of a group” option.
    For more information about how to work with list, please refer to:
    Adding a List
    If you have any further questions, please feel free to ask.
    Regards,
    Mike Yin

Maybe you are looking for

  • Upgraded to Itunes 6.01 and can't play songs

    I updated to Itunes 6.01 and now I can't play any music be it the music store or my ipod. I did the troubleshooting for windows xp and it still doesn't work. Please help!

  • ** Exception Throw in Fork Step - How to inform ?

    Hi Friends, Customer sends 2 IDoc DEBMAS, ADRMAS. The conditions is when both the IDocs is having the same customer no we need to send to the outside system.  (DEBMAS - E1KNA1M - KUNNR) equals to (ADRMAS - E1ADRMAS - OBJ_ID). I have designed BPM for

  • Error in validation (Using struts)

    Hi, struts-config.xml <action-mappings>                <action path="/userRegistration"                          forward ="/displayAddProdutForm.jsp"/>                        <action path="/saveProduct"                   name="productForm"           

  • Multiplexer error - error during formatting

    Hi gang This is an ongoing saga the last couple of days. This morning (using a new user account due to previous problems) set up an iDVD 08 project which is 4.25 gigs in size. If I burn it in high quality or prof. quality the size of the file drops t

  • Trying to set up 2 step verification.  After verifying my recovery key, it takes me to log in screen "your session has timed out".

    What the **** is happening?????  I have done this twice and I am now in possession of 2 recovery keys that I am paranoid to throw away.  I just want to set up this 2 step verification and go back to living my life?  Why is this so **** hard??????  I