atg fullfillment administration from AdminUI

-

Login to Admin UI,click Commerce Administration-Fullfillment Administration.


Click the link under List Shippable Groups to view the list of
shipping groups that are pending shipping.The list would be
ideally empty.

Now Go to your application and place an order with a single shipping
group.

Go to ACC and refresh the list of hardgood shipping groups.Select
the new shipping group.The status should be INITIAL,Refresh and within
a short time you can see the status change to PROCESSING and to PENDING_SHIPMENT.

Go back to Admin UI-Shippable Groups,You should see your shipping 
group awaiting shipping.

Go to the section Notify Fullfillment of shipment,fill the OrderID and
ShippingGroupId from the above table and click the Ship button.which
will notify the fullfillment system that the given shipping group has
been shipped to the customer.

Notify Fullfillment of shipment













Go back to ACC and refresh the view of the shipping group one more time.The status should now be NO_PENDING_ACTION.

Note:We have an option to Reprocess Shipping Groups as well.The Fullfillment Administration form will send a ShippingGroupUpdate message with the given data. A ShippingGroupUpdate message will tell the fulfillment system that the given shipping groups have been changed and need to be reprocessed. The order id given should be the order containing all of the shipping groups listed. List as many shipping group ids as necessary, separated by spaces.

Comments

Post a Comment

Popular posts from this blog

Weblogic Issues during EAR Deployment Exception in AppMerge flows progression

-
Unable to access the selected application Exception in AppMerge flows progression Bean already exists "weblogic.j2ee.descriptor.ModuleBeanImpl@..../Modules[weblogic.descriptor.internal.Descriptor.Beankey@....] This issue can happen in many scenarios, may be you need to check your deployment descriptors based on Application Servers used, this generally happens due to issue in XML files related to deployment. I got this issue when i mistakenly added the modules twice in the Manifest file, the module 'Store.Storefront' is added more than once in  'ATG-Required'  of my Manifest.MF file,due to this i am seeing the module 'storedocroot.war' is added twice in my application.xml which is located in the  path ATGProd.ear\META-INF\application.xml.Due to this i am not able to deploy my EAR file. I have removed the duplicate entry and deployed the application and everything working fine. ....... <module>         <web>             <web-uri>atg_
Read more

BCC site status inaccessible Agent Production in error state

-
Image
The Error Message showing in BCC T he error logs is showing the below message /atg/epub/DeploymentServer Failed to connect to agent 'Production'. This agent not allowed to be absent for  a deployment. The server will continue attempts to  intialize the connection. Set loggingDebug to true for  continued exception and stacktrace logging. Analysis This happens when the target/Production instance is down for some  reason or the RMI configuration which points to the target/Production instance may not be correct one. Fix If this is happening  due to target/Production instance down  then we can restart the target/Production Server,Other wise  correct the RMI configuration from the BCC agent configuration page and reinitialise. Verify the RMI Port in Configuration.properties file.Usually this file will be located in the path C:\ATG\ATG10.2\home\servers\ATGProduction\localconfig\atg\dynamo\Configuration.properties,make sure the
Read more

DUseSunHttpHandler=true weblogic.net.http.SOAPHttpsURLConnection Weblogic/Java HttpHandler issues

-
Verify the issue is happening due to the error throwing  from the weblogic class  SOAPHttpsURLConnection,then you need to inform the Application Server which handler implementation you need to use.  add the following option to JAVA_OPTIONS in   setDomainEnv.sh/setDomainEnv.cmd  on Unix/Windows.   -DUseSunHttpHandler=true.  eg:  set JAVA_PROPERTIES=%JAVA_PROPERTIES% %WLP_JAVA_PROPERTIES%  set JAVA_OPTIONS=%JAVA_OPTIONS% %JAVA_PROPERTIES% -  DUseSunHttpHandler=true -Dwlw.iterativeDev=%iterativeDevFlag% -  Dwlw.testConsole=%testConsoleFlag% -Dwlw.logErrorsToConsole=%  logErrorsToConsoleFlag%  This setting tells WebLogic to use the Sun's https Handler   implementation rather than the WebLogic one.  So after this,it will use the  class HttpsURLConnection from the  javax package.   See Also   SSL Handshake error   java.lang.RuntimePermission modifyThread
Read more