2016 - 宝洁 - 校招岗位【合集】 - 乔布简历
打开微信，扫描二维码
点击微信右上角，分享到朋友圈
宝洁在中国：
宝洁公司始创于1837年，是世界上最大的日用消费品公司之一。宝洁公司通过其旗下品牌服务全球大约四十八亿人。公司拥有众多深受信赖的优质、领先品牌，包括帮宝适、汰渍、碧浪、护舒宝、潘婷、飘柔、海飞丝、威娜、佳洁士、舒肤佳、玉兰油、SK-II、欧乐B、金霸王、吉列、博朗等等。宝洁公司在全球大约七十个国家和地区开展业务。
一九八八年，宝洁公司在广州成立了在中国的第一家合资企业－广州宝洁有限公司，从此开始了其中国业务发展的历程。宝洁大中华区总部位于广州，目前在广州、北京、上海、成都、天津、东莞及南平等地设有多家分公司及工厂。
申请前先看看宝洁最全求职攻略，戳这里↓↓↓，投递成功率更高哦！
Q1：我怎么样才能找到我想申请的职位？
A1：请按你所想申请的职位类型在“Job Openings”下的“Location”, &Job Field&及“Job Type”做对应的选择进行职位搜索。假如你知道你所申请的职位编号也可以在“Job Number”处直接输入职位编号，然后按搜索。
如你想申请校园招聘的职位，可以按以下指引进行职位搜索:
在“Location”项选择“China”;“Job Field”项不作选择，在“Job Type”项选择“Standard” (如申请全职职位) 或“Internship”（如申请实习生职位）,然后点击“放大镜” 按钮。
Q2：登陆时发现忘记了密码或忘记用户名，怎么办？
如果你忘记用户名，请在登陆界面点击“forget your user name”按钮，按照提示输入你注册时的email地址便可。
如果你忘记了密码，请在登陆界面点击“forget your password”按钮，按照提示输入你的用户名和注册时的email地址，系统便会把新的密码发到你的邮箱处。请在收到新的密码后及时修改你的密码。
如果发现用户名和邮箱地址不匹配，请先通过邮箱确认你的用户名信息，然后再在登陆界面点击“forget your password”按钮设置你的新密码。此操作也适合于账号被锁。
修改密码时请注意以下密码设定的格式要求
Please note that the password must respect the following rules:
It must contain between 6 and 32 characters. Use only characters from the following set: ! # $ % & ( ) * + , - . /
: ; & = & ? @ ABCDEFGHIJKLMNOPQRSTUVWXYZ [ \ ] _ ` abcdefghijklmnopqrstuvwxyz { | } ~
It must contain at least 1 letter(s) (ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyz).
It must contain at least 1 numeric character(s) ().
It must not contain more than 2 identical consecutive characters (AAA, iiii, $$$$$ ...).
It must not contain your user name.
对于无法登陆自己邮箱找回密码的申请人，请发送以下网申信息到宝洁的邮箱gcrecruit.，并邮件主题标明“更改申请账户信息”，我们会把重置的密码发到你新指定的邮箱，并把你的网申邮箱信息进行更新。在你收到密码重置邮件后，请使用你新的邮箱地址登录，并完成余下的网申流程。如果你不能提供以下信息，我们将无法帮你找回旧账号的信息。请务必保管好你的账户信息。
- 旧的网申邮箱地址：
- 新的网申邮箱地址：
- 你的中文名：
- 你的身份证号码：
Q3：如果想更换注册邮箱信息，怎么办？
A3：如果你过去曾经申请宝洁并在宝洁网申系统上使用邮箱注册过，现在由于各种原因需要修改你的邮箱地址，请先用原来的电子邮箱地址登录来进行修改：
如果你需要申请职位，请先申请你感兴趣的职位，在进入您的个人信息页面后，把您的电子邮件地址改为新的电子邮件地址，然后按照系统提示完成整个网申流程。
如果你已经申请了职位，请在My Jobpage中的My Submissions里，找到您已申请的职位，进入个人信息页面，把您的电子邮件地址改为新的电子邮件地址，其他信息保留不便并提交。如果你之前已经完成了网申测试，那么成绩将保留，信息修改后不需要重新做测试。
Q4：在申请校园招聘职位“Full time Entry Level Manager”或“Intern”时，城市选择问题所列的城市代表将来工作地点吗？
A4：不是。我们现在在网上所列的各个城市选项是指我们会在这些城市进行“Full time Entry Level Manager” 或“Intern”职位的校园招聘，假如您申请了某个城市的“Full time Entry Level Manager” 或“Intern”职位， 那你将参加这个城市的招聘程序，在此城市参加我们的笔试，面试等等。但这并不是指你将来的工作地点在这个城市。假如你所申请的职位的城市跟你所在的城市不同，由此而发生的你参加初次面试的差旅费是需要你本人自付的。而参加最后一轮面试及中文笔试的费用及则由宝洁公司报销。
如果你目前正在香港或海外城市，请选择香港或海外城市选项，我们将在有需要安排面试时与你联系，并确定面试地点。
Q5：我可以同时申请几个招聘城市的职位吗？
A5：你只可以申请一个城市的职位, 如果需要更改城市，请在网申结束前登陆你的个人信息页面进行修改。请注意你申请的城市只能是有计划进行校园招聘程序的城市，而不是指该职位的工作地点。一旦申请了相应的招聘城市的职位，将无法删除，你今后所有的招聘流程将在该城市发生，请在网申前仔细考虑清楚。
Q6：网上申请时选择部门时有什么规定吗？
A6：你只能申请在你所申请的城市有计划进行招聘的部门。如果你想申请其他部门，你只能申请与你最近的其他城市的职位并到该城市参加招聘的流程安排。在网申期间，你可以进入你的个人页面进行部门申请的修改。但网申结束后，部门信息将不能再修改，这将是你最终的选择，请慎重。如果申请了不在招聘计划的部门，你将可能在网申结束后被进行统一分配或终止申请。
Q7：我可以同时申请几个职位吗？
A7：同一时间，你只能参加一个职位的招聘流程。为了不影响你的职位申请，请同一时间内只申请一个职位。如在网申期间误申，请在网申截止前发邮件到 gcrecruit. 告知我们并附上以下信息，我们将视实际情况作出相应处理。
- 你的网申邮箱：
- 误申的职位：
- 希望申请的职位：
- 每个职位现网申状态：
Q8：填写手机号码（mobile phone number）时要注意什么？
A8：我们的笔试/面试邀请将都采用手机短信+邮件形式通知，请在填写手机电话号码时填写标准手机号码格式，如138XXXXXXXX,前面不用加86或0或区号,号码间不需要加横线或其他符号。并请确保你的手机号码能正常接收中国大陆发出的短信。如需更改你的手机联系方式，请在网申截止前进入你的个人信息页面，修改你的手机联系方式，并重新提交你的个人信息。如因号码填写错误错过任一招聘环节，将不再另作安排。
Q9：如果找不到我所属的专业或者学校，怎么办呢？
A9：在填写专业或学校的时候，如果找不到你所属的专业或者学校，请在文本框上输入关键字“not in list”并点击“Select” 。请尽量从学校名单中找到你所属的学校名称并选择，以便我们更清楚了解你的学校信息。
Q10：必须上传简历吗，简历必须英文吗?
A10：由于我们需要转载申请者的简历给面试官做面试准备，请务必在我们的系统上传你的简历。可上传中英文简历各一份。当你上传附件时，最多可以上传不超过5个附件。每个附件的大小不能超过500k。
Q11：宝洁承认哪些英文证书？
A11：宝洁在招聘中认可以下几类英语证书：
大学英语四六级证书
专业四八级英语证书
宝洁从2014年起,在校园招聘中取消英文考试环节，假如你曾经取得以上英语证书，请在回答英语考试证书问题时如实提供你的考试信息及证书成绩, 我们将使用您提交的英语成绩作为您英语能力的衡量依据。
请只提供有效的英语证书成绩且是总成绩，我们不接受估算的英语能力成绩。
网上填写的英语成绩必须真实。请注意我们稍后会委托51job要求你提供考试证书以验证成绩，若不能提交成绩单/证书的，或你网上填写的成绩与我们验证不符的，我们将立即终止你的申请流程。若不能在网申结束前提供证书，通过电子系统查询的证书信息均能认可。
如果你提交的证书成绩达到我们的要求，网申结束后，将有专门的同事通知你提交相关证书的电子信息，请耐心等待并留意你的邮箱信息。
Q12：为什么有的申请者有两个测试链接，有的只有一个，有的一个也没有收到呢？
A12：a) 背景介绍：
在您提供完您的个人信息并回答基础问题后，假如您对基础问题的回答符合我们的要求，您会进入到网上测试页面，如下图：
你可以选择点击“CLICK HERE-ASSESSMENT CENTER(在 ACTION REQUIRED!下面)”的链接直接开始做测试，或者点击“Request My Personal Assessment Link”要求系统把测试的链接通过email发到你的邮箱。请注意，若不点击“Request My Personal Assessment Link”，系统将不会向你邮箱发送测试链接的。若选择把测试链接通过email发到你的邮箱，在邮件中打开链接时，在输入你的用户名和登录密码后，页面将会自动跳转到测试页面。我们建议你直接完成测试，因为由于邮件屏蔽的原因，我们的系统不能对部分邮箱正常发送电子邮件。请注意，当你进入推理测试页面后，系统会自动检测你电脑的性能是否满足稍后的测试所需的电脑设置最低要求，如不更改，将无法继续完成测试。
另外在做测试的过程中请不要急着关闭网上测试链接页面，如果你在测试过程中断线，可点击页面上的测试链接重新进入测试页面。
b) 为什么我没有收到测试链接？
- 假如你是第一次申请我们公司的职位，且您对基础问题的回答不能符合我们的要求，您不会收到我们网上测试的要求，而直接进入“Complete“的页面。如左图。我们欢迎您一年以后再申请我们公司别的职位。
- 假如你在一年内在曾经网上申请过宝洁并且完成了两个网申测试，那么你不需要重做我们的网上测试，请按照系统提示完成网申便可. 你以往的成绩将记录在系统上。
- 当你完成基础问题，进入网上测试页面并点击CLICK HERE-ASSESSMENT CENTER
的链接后，将出现以下提示页面，由于你不需要重做测试所以两个测试的链接会自动成为灰色（如图），你只需要直接退出此页面即可完成此次网申。
- 如果你在一年内曾完成过我们任一个网申测试（管理成功能动性评估或推理测试)，那么这次你只需要完成另外一个测试就可以了，之前的分数将会保留。个别职位只需要完成一个网申测试，请按照系统提示完成网申便可。
如果你曾经在过去一年内，参加了宝洁任何一个职位的招聘流程（包括笔试/面试），并且在其中一个环节内被拒，这次是不可以再申请我们公司的职位的，本次申请将被视为无效。请在距上次申请一年后才能再申请我们其他职位。
一年内是指自你上次完成网申后的一年。例如你去年是日完成申请的，那么今年只能在日才能重新提交你的申请。网申必须在网申截止日期前提交才有效。如果由于距离上次申请不满一年而无缘今年招聘的同学，我们欢迎你能继续关注宝洁的其他职位招聘。
- 如果你曾经在过去一年内，参加了宝洁任何一个职位的招聘流程（包括笔试/面试），并且在其中一个环节内被拒，这次是不可以再申请我们公司的职位的，本次申请将被视为无效。请在距上次申请一年后才能再申请我们其他职位。
- 一年内是指自你上次完成网申后的一年。例如你去年是日完成申请的，那么今年只能再日才能重新提交你的申请。网申必须在网申截止日期前提交才有效。如果由于距离上次申请不满一年而无缘今年招聘的同学，我们欢迎你能继续关注宝洁的其他职位招聘。
Q13：重新提交个人信息后，再次出现测试链接，还需要再重做吗？
A13：是不需要的。当你重新提交个人信息，进入网上测试页面并点击CLICK HERE-ASSESSMENT CENTER
的链接后，将出现如图的提示页面，由于你不需要重做测试所以两个测试的链接会自动成为灰色，你只需要直接退出此页面即可完成此次网申。
Q14：为什么我点击了网上申请指南下方的“申请职位”键后，一直不能连接到下一页（或出现网页错误的提示）？
A14：请问您是通过校园网来上网进行申请的吗？当你点击“申请职位”的键后，我们的系统会把你的网页链接到我们公司在国外的网上申请系统的平台，而由于部分校园网是限制您登陆国外的网站的，所以当你点击了“申请职位” 键后，系统会进入死机或网页错误的状态。建议您用代理号上网或在校外上网。很抱歉由此而给你带来的不便。
Q15：我在申请过程中，出现以下页面，一直无法进入测试页面，该怎么办呢？
A15：为了保证网申测试顺利完成，我们的系统会在你进入测试页面之前进行系统检查，如果你的浏览器不符合系统的最低要求或启动了弹出窗口阻止程序，将进入左图页面:
- 若浏览器不符合系统要求：请下载支持的浏览器或下载更新版本的浏览器。
Internet Explorer 9 或以上
Chrome 21 或以上
Firefox 19.0 或以上
Mac 请使用 Safari 3.1或以上 （Safari在Windows上暂不支持使用）
- 若启用了弹出窗口阻止程序：请关闭弹出窗口阻止程序。
方法如下：
工具-&弹出窗口阻止程序-&关闭弹出窗口阻止程序或在留意浏览器的右上角
请在确保你的浏览器满足以上设置后，重新点击以下页面的测试链接，便可顺利进入测试页面。
Q16：我在收到宝洁公司的网上测试/On-line Assessment 的电子邮件后，点击网上测试的链接，但不能成功链接到下一页或出现错误页面，该怎么办？
A16：a) 请问你是通过校园网或局域网打开此链接吗？由于我们的网上测试是处于国外的系统平台，而由于校园网或部分其他网路会限制您登陆国外的网站的，所以当你点击了链接后，系统会进入死机或网页错误的状态。建议您用代理号上网或在校外上网。很抱歉由此而给你带来的不便。
b) 如果你不是使用上述网络登陆但又出现以上情况的，将可能是以下原因导致：
- 网速过慢。为了确保评估的有效开展，我们建议使用至少56KBPS的链接速度。请更换你的网络。
- 启用了弹出窗口阻止程序:请关闭弹出窗口阻止程序。
(方法如下：工具-&弹出窗口阻止程序-&关闭弹出窗口阻止程序 或 在留意浏览器的右上角)
- 网页被防火墙屏蔽或缺少某个控件的安装. 只要把导致屏蔽的防火墙关掉或者按提示安装上控件便可。提示一般会出现在浏览器的右上方
- 浏览器安全级别设置为高,请把级别设置为中以下.
- 请下载支持的浏览器或下载更新版本的浏览器，本网站不支持MAC自带的浏览器，请不要使用MAC登录本网站
Internet Explorer 9 或以上
Chrome 21 或以上
Firefox 19.0 或以上
Mac 请使用 Safari 3.1或以上 （Safari在Windows上暂不支持使用）
c) 如果设置已经更改，但仍然无法进入测试页面，请换另外一台电脑和网络尝试。
如果上述操作均无效，请把你的情况用英文描述并附图发到该邮箱：careers.， 我们国外有专门的技术部处理你的情况的。
A17：我在申请的过程中断线了，该怎么办？
Q17：a) 你可以点击测试页面的测试链接重新进入
b) 如果你有申请把测试链接发到你的邮箱，可以直接点击邮件的测试链接重新进入。中断前的结果将会被保留，请继续把没有完成的题目完成。
如果测试页面已经关闭，请你重新回到Job Search 页面，然后按右上角的My Job Cart ，点击My Jobpage中的My Submissions，找到你申请的职位，点击view submission并重新提交，然后你会重新进入如图页面：
请回到你断线的地方并继续申请，你之前所做的操作也会被保留。在做测试的过程中请不要急着关闭网上测试链接页面，如果你在测试过程中断线，可点击上述页面上的测试链接重新进入测试页面。
A19：我要在完成申请后多久才能收到宝洁公司的邮件？
Q19：在完成您的资料填写申请后的大概24小时后您的电子邮箱就会收到我们的邮件。当你完成管理成功能动性评估和推理测试后系统会给你发送确认邮件，但是如果你的邮箱对我们发出的邮件进行屏蔽或你的邮箱信息填写有误,那么系统将不能向您正常发送电子邮件。
Q20：为什么我没有像别人那样在我的Email/电子邮箱里收到宝洁公司的电子邮件？
A20：a) 请先检查您注册的邮箱是否填写正确。
b) 请检查垃圾邮件箱，广告邮件箱，检查邮箱是否把宝洁公司的电子邮件屏蔽了
如果完成上述检查，仍然收不到我们的邮件。请用原来的电子邮箱地址登录，在My Jobpage中的My Submissions里，找到您申请的职位，进入您的个人信息页面时，把您的电子邮件地址改为新的电子邮件地址，其他信息保留不便，然后像上一次那样完成整个申请流程提交便可。如果你之前已经完成了网申测试，那么成绩将保留，信息修改后不需要重新做测试。
Q21：请问校园招聘的招聘对象是什么？网申时候是什么时候结束？
全职经理 Full time Entry Level Manager（面向当年应届毕业生〕
暑期实习生Summer Intern (面向次年应届毕业生〕。
宝洁校园招聘网申的时间从9月9日开始，10月10日晚上24:00结束。请大家在网申时间内完成所有的网申流程。如果不能在网申时间内把整个网申流程完成，你将不能进入下一招聘环节。有关一年内申请的问题请查看“过去曾经申请宝洁职位如何参加相关应聘程序”部分。
Q22：过去网申过宝洁并已进入笔试/面试，为什么一年后还收到测试的链接？
A22：是会收到的。我们的网申成绩只保留一年，请按照系统的提示把测试重新完成。
Q23：过去我曾经通过宝洁网申，并进入笔试/面试环节，那么我这次一定也可以进入该招聘环节吗？
A23：不一定的。由于每一年的招聘要求都有不同，因此过去进入任一招聘流程的同学，不代表这次就必定能进入该招聘环节的。因此希望同学们都能认真对待本次每一个招聘环节，根据网申提示完成所有招聘流程。
Q24：如果我之前曾经申请过宝洁公司的职位，这次可以重新申请吗？
A24：首先请注意：请继续使用以前的申请账号完成这次的申请。每人只能用一个email地址注册，账号一旦创建将无法删除。假如我们发现您使用了多于一个地址注册，则视您的所有申请无效。
a) 如果你是在距这次申请一年内曾经申请我们公司的任何职位并已被拒，需在距上次申请一年后才能再次申请我们的职位。
b) 如果你是在距这次申请一年内曾经申请我们公司的任何职位，但是没有进入任何一个招聘流程（笔试/面试），那么这次请继续使用同一个账号申请今年感兴趣的职位，并按照系统提示提交这次网申，你是不需要重新完成网上两个测试的（成功驱动力测试和推理测试）。如果你通过我们的筛选，网申截止后将有同事通知你下一招聘流程的安排.
c) 如果你在距这次申请一年以上曾经申请我们公司的任何职位，无论是否参加过任何招聘环节，请继续使用同一个账号申请这次感兴趣的职位，并按照系统提示再次进行测试以完成这次网申。如你上次申请已进入任一招聘环节（笔试/面试），我们会按照今年的招聘要求来确定你是否需要重新参加笔试或面试。
请注意： 只要你在距这次申请一年以上，无论过去的申请曾经进入到任何一个阶段，只要通过系统基础问题回答的筛选环节，系统都会向你发送网申测试链接，请把测试链接重新完成。
Q25：海外学生怎样参加中国本土的校园招聘？
A25：如果你目前正在香港或海外城市，请在回答基础问题时，招聘城市处选择香港或海外城市选项，我们将在有需要安排面试时与你联系，并确定面试地点。
Q26：请问网申通过名单会用什么方式公布呢？
A26：我们的面试/笔试的通知都主要以短信和邮件结合方式公布，请大家在网申时务必认真填写，确保信息正确，在填写手机电话号码时请填写标准号码格式，如138XXXXXXXX,前面不用加86或0或区号,号码间不需要加横线或其他符号；并请请确保你的手机号码能正常接收中国大陆发出的短信。如需更改你的手机联系方式，请在网申截止前进入你的个人信息页面，修改你的手机联系方式，并提交。如因联系方式填写错误而错过任一招聘环节，将不再另作安排。敬请谅解job entry time
作业输入时间
作业输入时间
基于3个网页-
Hello Welcome to Page "Actew" for entry level jobs full-time or part-time job or work in Toronto, ON, Canada.
欢迎来到 Actew页的招聘信息为入门级的位置或全职工作或兼职工作在多伦多，ON，加拿大。
Community colleges offer a degree after the completion of two years of full-time study. They frequently offer technical programs that prepare students for immediate entry into the job market.
社区学院一般两年学习后发给文凭， 有点像我国的技工学校， 学生毕业后就可以进入就业市场。
After about a year of full-time work, one of my Internet friends left his entry-level job at Cato, and encouraged me to apply to be his successor.
$firstVoiceSent
- 来自原声例句
请问您想要如何调整此模块？
感谢您的反馈，我们会尽快进行适当修改！
请问您想要如何调整此模块？
感谢您的反馈，我们会尽快进行适当修改！Oracle Order Management Implementation Manual
Browser version script Oracle Order Management SetupThis chapter covers the following topics:
Overview of Setup
This chapter explains how to set up and implement Oracle Order Management. The Oracle Order Management Application provides many flexible features enabling you to set up your system to begin processing order information. You must define your business order policies, such as how you classify your orders, as well as various control features prior to processing orders within the application.
Please refer to the Oracle Applications Multiple Organizations Implementation Guide for more information on setting up multi-org access control.
In addition to reading this chapter, please refer to the Using Oracle Workflow in Oracle Order Management manual for setup and implementation details for Order Management workflows.
Setup Steps
Oracle Order Management Recommended Implementation
Order Management Setup Steps
Setup Steps Defined in Detail
Profile Options
Oracle Order Management Recommended Implementation
Implementation involves several phases, including setting up other integrated applications, which include Multi-Org Access Control (MOAC), Oracle General Ledger, Oracle Receivables, and Oracle Inventory. Some setup steps are optional, depending on whether you have the integrating applications installed and whether you use the associated feature. For example, if your business supports drop shipments, you should also set up Oracle Purchasing. If you sell models and kits, set up Oracle Bills of Material and Oracle Configurator.
If you are using a multiple organization structure, your system administrator must set the parameter OM: Item Validation Organization. This enables Order Management to default code and revenue account information accurately.
Set Up Oracle Applications Technology
The setup steps in this chapter tell you how to implement the parts of Oracle Applications specific to Oracle Order Management. This includes:
Performing system-wide setup tasks, such as configuring concurrent managers and printers
Managing data security, which includes setting up responsibilities to enable access to a specific set of business data and transactions, and assigning individual users to one or more of these responsibilities
Also, if your product uses Oracle Workflow, for example, to manage the approval of business documents or derive Accounting flexfield values via the Account Generator, you need to set up Oracle Workflow.
Order Management Setup Steps
The following table displays a list of all the implementation steps for Oracle Order Management and a reference to documentation that can help to accomplish the steps.
Optional or Required
1.Define multiple organizations in Oracle Inventory
Oracle Inventory User's Guide
2. Setup Multi-Org (Multiple Organization) Access Control
Oracle Applications Multiple Organizations Implementation Guide
3. Define key and descriptive flexfields
Oracle Order Management Implementation Manual
required under certain conditions
4. Define inventory organizations (warehouses), parameters, subinventories, and picking rules in Oracle Inventory
Oracle Inventory User's Guide
Oracle Order Management Implementation Manual
Oracle Order Management Implementation Manual
7. Define invoicing information
Oracle Order Management UserGuide
required under certain conditions
8. Define your sales representatives
Oracle Receivables Implementation Guide
Current, Oracle Receivable's User's Guide
Oracle Order Management Implementation Manual
required under certain conditions
11. Define header and line processing flows
Oracle Order Management
Oracle Order Management Implementation Manual
Oracle Order Management Implementation Manual
required under certain conditions
14. Define the units of measure
Oracle Inventory User's Guide
15. Define item information
Oracle Inventory User's Guide
16. Define the items that you sell
Oracle Inventory User's Guide
17. Define the configurations that you sell
Oracle Bills of Material User's Guide
required under certain conditions
18. Define price lists
Oracle Advanced Pricing Implementation Manual
19. Define customer profile classes
Oracle Receivables Implementation Guide
required under certain conditions
20.Define information on your customers
Oracle Receivables Implementation Guide
21. Define item cross references
current, Oracle Inventory User's Guide
required under certain conditions
22. Define your sourcing rules
Oracle Advanced Planning and Scheduling User's Guide
Oracle Order Management Implementation Manual
24. Set up Cost of Goods Sold Accounting flexfield combination
Order Inventory User's Guide
required under certain conditions
Oracle Order Management Implementation Manual
Oracle Order Management Implementation Manual
Oracle Order Management Implementation Manual
required under certain conditions
Oracle Order Management Implementation Manual
required under certain conditions
Oracle Order Management Implementation Manual
Oracle Order Management Implementation Manual
31. Define shipping parameters
Oracle Shipping Execution User's Guide
Setup Steps Defined in Detail
The following is a list of each setup step defined in detail.
Step 1: Multiple Organizations
Define multiple organizations in Oracle Inventory. This step is required.
Step 2: Multi-Org Access Control
The Multi-Org Access Control (MOAC) feature enables users to access to one or more Operating Units within one user responsibility. Please refer to the Oracle Applications Multiple Organizations Implementation Guide for more information.
Step 3: Flexfields
Define key and descriptive flexfields to capture additional information about orders and transactions.
This step is required for Key Flexfields, and optional if you plan on using the functionality surrounding Descriptive Flexfields. Several defaulting values are provided.
Step 4: Inventory Organizations
Define inventory organizations (warehouses), parameters, subinventories, and picking rules in Oracle Inventory.
You must define at least one item validation organization and at least one organization that acts as an inventory source for orders fulfilled internally. If you plan to drop ship some orders, you must also define at least one logical organization for receiving purposes. Your item validation organization can be the same as your inventory source or your logical receiving organization, but you cannot use one organization for all three purposes. See Step 5 for setting your item validation organization.
This step is required.
Step 5: Profile Options
Define profile options to specify certain implementation parameters, processing options, and system options.
This step is required.
Step 6: Parameters
Set your Order Management System Parameters to validate items, enable customer relationships, and operating unit defaults.
This step is required.
Step 7: Invoicing
Define invoicing information, including payment terms, invoicing and accounting rules, Autoaccounting parameters, territories, and invoice sources.
This step is required if you plan on transferring invoicing information to Oracle Receivables. Several defaulting values are provided.
Step 8: Salespersons
Define information on your sales representatives.
This step is optional.
Step 9: Tax
Define tax features, such as codes, rates, exceptions, and exemptions.
This step is required.
Step 10: QuickCodes
Define QuickCodes that provide custom values for many lists of values throughout Order Management.
This step is required if you plan on creating user defined Quickcodes for utilization within Order Management. Defaulting values are provided.
Step 11: Workflow
Define header and line processing flows to meet different header and line type requirements.
This step is required.
Step 12: Document Sequences (Order Numbering)
Define Document Sequences for automatic or manual numbering of orders.
This step is required.
Step 13: Order Import Sources
Define sources for importing orders into Order Management.
This step is required if you plan on importing orders or returns into Order Management.
Step 14: Units of Measure
Define the units of measure in which you supply items.
This step is required.
Step 15: Item Information
Define item information, including item attribute controls, categories, and statuses.
This step is required.
Step 16: Items
Define the items that you sell, as well as container items.
This step is required.
Step 17: Configurations
Define the configurations that you sell.
This step is required if you plan on generating orders or returns for configured items. Several defaulting values are provided.
Step 18: Pricing
Define price lists for each combination of item and unit of measure that you sell. Optionally, you can define pricing rules and parameters to add flexibility.
For more information about pricing setup and implementation, refer to the Oracle Advanced Pricing Implementation Manual.
This step is required.
Step 19: Customer Classes
Define customer profile classes.
This step is required if you plan on using the functionality surrounding Customer Profiles. Several defaulting values are provided.
Step 20: Customers
Define information on your customers.
This step is required.
Step 21: Item Cross References
Define item cross references for ordering by customer part number, UPC, or any generic item number.
This step is required if you plan on using the functionality surrounding item cross referencing. Several defaulting values have been provided.
Step 22: Sourcing
Define your sourcing rules for scheduling supply chain ATP functions.
This step is optional.
Step 23: Order Management Transaction Types (Sales Documents)
Define Order Management transaction types to classify sales documents. For each order type, you can assign a default price list, defaulting rules, order lines, return lines, line types, workflow assignments, payment terms, and freight terms.
Note: Order Management provides NO seeded OM transaction types. For existing Oracle Order Entry customers, Order Management will update existing Order Types to OM transaction type during the upgrade process.
This step is required.
Step 24: Cost of Goods Sold (COGS)
Set up your Cost of Goods Sold Accounting Flexfield combination (COGS Account) in Oracle Inventory.
This step is required if you plan on utilizing the functionality surrounding COGS.
Step 25: Processing Constraints
Define processing constraints to prevent users from adding updating, deleting, splitting lines, and cancelling sales documents information beyond certain points in your business flows. Use the constraints Order Management provides, which prevent data integrity violations, or create your own.
This step is optional. Several default values for processing constraints have been defined.
Step 26: Defaulting Rules
Define defaulting rules to determine the source and prioritization for defaulting order information to reduce the amount of information you must enter manually in the Sales Orders window.
This step is optional. Several Defaulting rules and corresponding values for have been defined.
Step 27: Credit Checking
Define your credit checking rules.
This step is required if you plan on performing any type of order credit checking.
Step 28: Holds
Define automatic holds to apply to orders and returns.
This step is required if you plan on performing automatic hold for orders or returns.
Step 29: Attachments
Define standard documents to attach automatically to sales documents.
This step is optional.
Step 30: Freight Charges and Carriers
Define freight charges and freight carriers to specify on orders.
This step is required if you plan on charging customers for freight or additional order charges.
Step 31: Shipping
Define shipping parameters in Oracle Shipping Execution.
This step is required.
Oracle Training Administration Users
Please refer to the Oracle Training Administration User's Guide for additional Order Management Setup Steps.
Oracle Process Manufacturing Users
Please refer to the Oracle Process Manufacturing guides for additional Order Management Setup Steps.
Related Documents
Oracle Shipping Execution User’s Guide
Oracle Inventory User’s Guide
Oracle Receivables User Guide
Oracle Receivables Implementation Guide
Oracle Receivables Reference Guide
Oracle Bills of Material User’s Guide
Oracle Order Management User’s Guide
Oracle Applications Multiple Organizations Implementation Guide
Using Oracle Training Administration
Related Topics
Holds and Releases
Profile Options
Setting OM System Parameters
Define Credit Checking Rules
Credit Checking
Define Defaulting Rules
Defaulting Rules
Define Processing Constraints
Processing Constraints
Define Order Management Transaction Types
Transaction Types
Setting up the Supply Chain
Setting Up Basic Pricing
Order Import
Define Document Sequences for Order Numbering
Using Workflow in Order Management
Define QuickCodes
Multi-Org Access Control
Please refer to the Oracle Applications Multiple Organizations Implementation Guide for general MOAC setup details.
To support Multi-Org Access Control the Operating Unit has been added to many of the Order Management windows. If you are enabling MOAC functionality for your implementation and you want to give your users the ability to enter and search sales order documents across Operating Units then you need to enable (make the field visible) the Operating Unit field in the various Order Management forms that are folder enabled.
It is recommended that the Operating Unit field should be the first visible field on a form, or the first field before an Operating Unit sensitive field. To make the hidden Operating Unit field visible in OA Framework (HTML) pages, you need to use the OA Framework Personalization feature.
The windows / OA pages where the Operating Unit is seeded as hidden:
Order Information Portal:
Sales Order Advanced Search and Results page
Order Status page
Deliveries Advanced Search
Delivery page
Sales Orders windows:
Sales Order window
Order Organizer Find window (All tabs)
Order Summary
Quick Sales Order window
Quick Sales Order Organizer
Quick Order Summary
Quote window
Quote Organizer
Quote Summary
Find Customer window
Sales Agreements windows:
Sales Agreements window
Sales Agreements Organizer
Sales Agreements Summary
Other windows:
Scheduling Organizer window
Pricing and Availability window
Order Import Corrections window
Open Interface Tracking window
Retrobill Organizer window, Retrobill Requests tab
The Order Management windows where the Operating Unit is added as visible:
Audit History Find, Audit History
Add Customer window
Apply Holds (Criteria tab) window
Approvals (to display Operating Unit of Transaction Type)
Export Compliance Find, Export Compliance Workbench
Order Import Corrections Find window
Open Interface Tracking Find window
Process Messages Find,
Process Messages window
Payment Types
System Parameters
Shipping Tolerances (to display Operating Unit of Customer Address)
Transaction Types
In the windows where the Operating Unit can be specified,
the list of values for the Operating Unit field is determined by the profile MO: Security Profile.
The field will have a default value based on the profile MO:
Default Operating Unit.
For details on MOAC setup please refer to the Oracle Applications Multiple Organizations Implementation Guide.
Profile Options
During implementation, you set a value for each user profile option to specify how Order Management controls access to and processes data. This is step four of the .
Generally, the system administrator sets and updates profile values. See: Setting Profile Options, Oracle E-Business Suite System Administrator's Guide - Maintenance.
Profile Categories
In the current release, profiles have been categorized so that they can be easily classified or grouped. The following table displays the profile categories and the profile options that belong to each one. Some profile options belong to more than one category and are indicated in the table below.
Profile Category Name
Profile Option(s)
Configurations
OM: Allow model fulfillment w OM: Configuration Quick S OM: Copy Model DFF OM: Included Item Freeze M OM: Party Totals C
Customer Usage
OM: Add Customer (Order Import);
OM: Create Account I
OM: E-Mail Required on New C
OM: Party Totals C OM: Sales Order Form: Restrict Customers
OM: Debug Log D
OM: Debug L
OM: Generate Diagnostics for Error A
Deployment
OM: Orders Purge Per C
OM: New EDI Acknowledgment F
OM: Printed Document Extension Class N
Electronic Messaging
OM: Change SO Response R
OM: Electronic Message Integration Event Sources OM: New EDI Acknowledgment F OM: Order Accept State for XML; OM: Run Order Import for XML;
OM: Send Acknowledgment for Change PO R
OM: Add C OM: Administer Public Q OM: Automatically Open Related Items W OM: Contact Center Actions Menu N OM: Cust Item Shows M OM: Display Actions Button vs. P OM: Display Current Selections in Pricing/A OM: Enable Related Items and Manual S OM: Item View M OM: Quick Sales Order Form: Auto R OM: Quick Sales Order Form: Defer P OM: Sales Order Form: Cascade Header Changes to L OM: Sales Order Form: Refresh Method (Query Coordination); OM: Sales Order Form: Restrict C OM: Sales Order navigation from Pricing/A OM: Sales Orders F OM: Scheduling R OM: Show Line D OM: Show Process Messages F OM: Use C OM: View Cancel L OM: View Closed L OM: View Pricing & Availability Information in Related I
Fulfillment
OM: Allow model fulfillment w OM: Included Item Freeze M OM: Over Return T OM: Over Shipment T OM: Population Of Buyer Code For Dropship L OM: Source C OM: Under Return T OM: Under Shipment T OM: Automatically Interface Lines to IB on Fulfillment
OM: Modify Seeded H OM: Prevent Booking for Line Generic H
OM: Interface freigh OM: Invoice Numbering M OM: Set Receivables Transaction Date as Current Date for Non-Shippable L OM: View Intercompany AR Invoice
Item Usage
OM: Customer Item Shows M OM: Enable Related Items and Manual S OM: Item F OM: Restrict Customer Items for Line Level Ship To A
OM: Sequence for TP Ship/Deliver D OM: Source for TP Early Ship/Deliver D
Order Import
OM: Add Customer (Order Import);
OM: Import Multiple S
OM: Unique Order Source, Orig Sys Document Ref Combination For Each C
OM: Commitment S OM: Credit Card P OM: Preserve External Credit Balances
OM: Customer Service F OM: Customer Service Report D OM: Records On Summary Page For External U
OM: Charges For B OM: Charg OM: Charging P OM: Discounting P OM: Enable Group pricing for DSP OM: Item Change Honors Frozen P OM: List Price Override P OM: Negative P OM: Promotion Limit Violation A OM: Send Changed Lines to P OM:Unit Price Precision T OM: UOM Class for Charge P OM: Price Adjustment Modifier for AIA Order Lines
OM: Customer Service F OM: Customer Service Report D OM: Over Return T OM: Notification A OM: Return Item Mismatch A OM: Return Unfulfilled Referenced Line A OM: Under Return T
Scheduling
OM: Assign New Set For Each L OM: Authorized To Override ATP; OM: Auto Push Group D OM: AutoS OM: Enforce Shipping Method for Ship S OM: Schedule ATO Item Without BOM; OM: Scheduling R
OM: Add C OM: Add Customer (Order Import); OM: Administer Public Q OM: Authorized To Override ATP; OM: Cascade S OM: Charging P OM: Create Account I OM: Credit Card P OM: Discounting P OM: List Price Override P OM: Modify Seeded H OM: Scheduling R OM: Authorized To Override ATP;
OM: Cascade S
Transaction Entry
OM: Apply Automatic A
OM: Cascade S
OM: Configuration Quick S
OM: Copy Mode
OM: Default Blanket Agreement T OM: Default Blanket Transaction P
OM: Default Sales Transaction P
OM: Default S
OM: Display New Order After Copy
OM:Enforce check for duplicate Purchase O
OM: Generic Update Constraints Apply to DFF?;
OM: Prevent Booking for Line Generic H
OM: Return Item Mismatch A
OM: Return Unfulfilled Referenced Line A
OM: Context Responsibility for Upgraded O OM: Notification A
Implementing Profile Options Summary
The following table indicates whether you can view or update the profile option and at which System Administrator level the profile options can be updated. The System Administrator level includes User, Responsibility, Application, and Site levels.
The table also displays if the profile option is Optional or Required:
Required: Requires you to provide a value
Optional: A default value is provided, so you only need to change it if you do not want to accept the default
If the profile option from the table is prefaced with an application short code, you can find additional information surrounding the profile option usage in the related Application User Guide.
The table also uses the following values to describe profile option controls for columns User, System Admin User, System Admin Resp, System Admin App, and System Admin Site:
Yes: You can update the profile option.
View Only: You can view the profile option value in the Profiles window, but you cannot change it.
No: You cannot view or change the profile option value.
For the profile options table below, the following codes are used to denote profile options used within Order Management that are defined within other Oracle Applications. See the appropriate User Guide for additional details.
(AR) Oracle Receivables
(BOM) Oracle Bills of Material
(FND) Oracle Applications Foundations
(GL) Oracle General Ledger
(INV) Oracle Inventory
(QP) Oracle Advanced Pricing
(WSH) Oracle Shipping Execution
(OKC) Oracle Sales Contracts
The following table is a more in-depth description of each of the profile options.
Profile Options
Profile Option Name
System Admin. User
System Admin. Resp.
System Admin. App.
System Admin. Site
Default Value
Profile Category Names
OM: Add Customer
Yes - default is None
Yes - default is None
Customer Usage, Security, Forms UI
OM: Add Customer (Order Import)
Customer Usage, Security, Order Import
OM: Administer Public Queries
Forms UI, Security
OM: Allow Model Fulfillment Without Configuration
Fulfillment, Configurations
OM: Apply Automatic Attachments
Transaction Entry
OM: Assign New Set For Each Line
Scheduling
OM: Authorized to Override ATP
Scheduling, Security
OM: Automatically Interface Lines to IB on Fulfillment
Fulfillment
OM: Automatically Open Related Items Window
OM: Auto schedule
Scheduling
OM: Auto Push Group Date
Scheduling
OM: Cascade Service
Null - equivalent to Yes
Service, Transaction Entry
OM: Change SO Response Required
Electronic Messaging
OM: Charges for Backorders
OM: Charges for included item
OM: Charging Privilege
Pricing, Security
OM: Commitment Sequencing
OM: Configuration Quick Save
Transaction Entry, Configurations
OM: Contact Center Actions Menu Name
ONT_CONTACT_CENTER_SUB_MNU
OM: Context Responsibility for Upgraded Orders
No Default
OM: Copy Model DFF To Child Lines
Transaction Entry, Configurations
OM: Create Account Information
Customer Usage, Security
OM: Credit Card Privileges
Payments, Security
OM: Cust Item Shows Matches
Item Usage, Forms UI
OM: Customer Service Feedback
Returns, Portal UI
OM: Customer Service Report Defect
Returns, Portal UI
OM: DBI Installation
Deployment
OM: Debug Level
OM: Debug log Directory
OM: Default Sales Transaction Phase
Transaction Entry
OM: Default Blanket Agreement Type
Transaction Entry
OM: Default Blanket Agreement Transaction Phase
Transaction Entry
OM: Default Salesrep
Transaction Entry
OM: Discounting Privileges
Pricing, Security
OM: Display Actions Button vs. Pop list
OM: Display Current Selections in Pricing and Availability
OM: Display New Order After Copy
Transaction Entry
OM: Electronic Message Integration Event Sources
Electronic Messaging
OM: E-Mail Required On New Customers
Customer Usage
OM: Enable Group Pricing for DSP Lines
OM: Enable Related Items and Manual Substitutions
Item Usage,
OM: Enforce Check For Duplicate Purchase Order
Transaction Entry
OM: Enforce Shipping Method for Ship Sets
Scheduling
OM: Generate Diagnostics for Error Activities
OM: Generic Update Constraints Apply to DFF?
Transaction Entry
OM: Import Multiple Shipments
Null - equivalent to No
Order Import
OM: Included Item Freeze Method
Fulfillment, Configurations
OM: Interface Freight Tax Classification Code From Line
OM: Invoice Numbering Method
OM: Item Change Honors Frozen Price
OM: Item Flexfield
System items
Item Usage
OM: Item View method
OM: List Price Override Privilege
Pricing, Security
OM: Modify Seeded Holds
Internal Use Only
Internal Use Only
Internal Use Only
Internal Use Only
Internal Use Only
Internal Use Only
Internal Use Only
Holds, Security
OM: Negative Pricing
OM: New EDI Acknowledgment Framework
Deployment, Electronic Messaging
OM: Notification Approver
Upgrade, Returns
OM: Order Accept State For XML
Null - equivalent to Entered
Electronic Messaging
OM: Orders Purge Per Commit
Deployment
OM: Over Return Tolerance
Returns, Fulfillment
OM: Over Shipment Tolerance
Fulfillment
OM: Party Totals Currency
US Dollars
Customer Usage
OM: Population Of Buyer Code For Dropship
Fulfillment
OM: Preserve External Credit Balances
OM: Prevent Booking for Line Generic Holds
Holds, Transaction Entry
OM: Price Adjustment Modifier for AIA Order Lines
OM: Printed Document Extension Class Name
Deployment
OM: Promotion Limit Violation Action
OM: Quick Sales Order Form: Auto Refresh
Application
OM: Quick Sales Order Form: Defer Pricing
OM: Records on Summary Page for External Users
OM: Restrict Customer Items for Line Level Ship To Address
Item Usage
OM: Return Item Mismatch Action
Returns, Transaction Entry
OM: Return Unfulfilled Referenced Line Action
Returns, Transaction Entry
OM: Run Order Import for XML
Electronic Messaging
OM: Sales Order Form: Cascade Header Changes to Line
OM: Sales Order Form Preference
Sales Orders
OM: Sales Order Form: Refresh Method (Query Co-ordination)
Null - equivalent to Automatic Refresh with Repositioning of Cursor
OM: Sales Order Form: Restrict Customers
Customer Usage
OM: Sales Order Navigation From P&A form
OM: Schedule ATO Item Without BOM
Scheduling
OM: Scheduling Role
Scheduling, Forms UI, Security
OM: Send Acknowledgment for Change PO Response
Null - equivalent to No
Electronic Messaging
OM: Send Changed Lines to Pricing
OM: Sequence for TP Ship/Deliver Deadline
OM: Set Receivables Transaction Date as Current Date for Non-Shippable lines
OM: Show Line Details
OM: Show Process Messages Flag
OM: Source Code
ORDER ENTRY
Fulfillment
OM: Source for TP Early Ship / Deliver Date
OM: Use Configurator
Deployment, Forms UI,
Transaction Entry, Configurations
OM: Use Materialized
View for Items LoV (Honours Item Orderability Rules)
Fulfillment
OM: Under Return Tolerance
Returns, Fulfillment
OM: Under Shipment Tolerance
Fulfillment
OM: Unique Order Source, Orig Sys Document Ref Combination For Each Customer
Order Import
OM: Unit Price Precision Type
OM: UOM Class For Charge Periodicity
OM: View Cancel Lines
OM: View Closed Lines
OM: View Intercompany AR invoice
OM: View Pricing/Availability Information in Related Items
Credit Limit Selection
AR: Item Flexfield Mode (AR)
AR: Use Invoice Accounting for Credit Memos (AR)
HZ: Generate Contact Number (AR)
NULL - equivalent to Yes
HZ: Generate Party Number (AR)
NULL - equivalent to Yes
HZ: Generate Party Site Number (AR)
NULL - equivalent to Yes
Tax: Allow Ad Hoc Tax Changes (AR)
Tax: Allow Manual Tax Lines (AR)
EBTax: Allow Override of Customer Exemptions (AR)
Tax: Allow Override of Tax Classification Code (AR)
Tax: Calculate Tax on Credit Memos (AR)
Tax: Use Tax PL/SQL Vendor (AR)
Tax: Use Tax Vendor (AR)
BOM: Check for Duplicate Configuration (BOM)
BOM: Component Item Sequence Increment (BOM)
BOM: Configurator URL of UI Manager (BOM)
BOM: Default Bill of Material Levels (BOM)
Sequential Numbering (FND)
Default Country (FND)
Flexfields: Open Descr Window (FND)
Journals: Display Inverse Rate (GL)
At site level
INV: Capable to Promise (INV)
OKC: Enable Sales Contracts (OKC)
QP: Accrual UOM Class (QP)
No Default
QP: Blind Discount Option (QP)
QP: Item Validation Organization (QP)
No Default
QP: High Volume Order Processing Compliance (QP)
QP: Line Volume UOM Code (QP)
No Default
QP: Line Weight UOM Code (QP)
No Default
QP: Negative Pricing (QP)
No Default
QP: Return Manual Discounts (QP)
QP: Source System Code (QP)
No Default
QP: Unit Price Precision Type (QP)
QP: Verify GSA Violations (QP)
WSH: Internet Proxy URL (WSH)
Order Management Profile Option Descriptions and Settings
OM: Add Customer
ONT_ADD_CUSTOMER
This profile option determines which users who can access the Order Management Add Customer window to enter customers, customer addresses, and customer contact information. Select from:
All: Users can create new customers, customer addresses, and customer contacts.
None: User cannot create new customers, customer addresses, and customer contacts.
Address and Contact only: Users can access the Add Customer window to create both new customer addresses and/or customer contacts for existing customers only
The default for this profile option is None.
Note: You cannot update existing customer information from the Add Customer window. However, if the e-mail address field is NULL for a customer and/or customer contact, you can update these fields.
Note: Oracle Trading Community Architecture provides a model for managing information about entities such as customers. The TCA Data Sharing and Security (DSS) feature allows you to define rules around who can create, update or delete customer data.For more information please refer to the Oracle Trading Community Architecture Administration Guide.
OM: Add Customer (Order Import)
ONT_ADD_CUSTOMER_OI
This profile option determines which users can create new customers and customer details when importing order using the Order Import concurrent program. Select from:
All: Users can create new customers, customer addresses, and customer contacts.
None: User cannot create new customers, customer addresses, and customer contacts.
Address and Contact only: Users can access the Add Customer window to create both new customer addresses and/or customer contacts for existing customers only
The default for this profile option is None.
Note: Oracle Trading Community Architecture provides a model for managing information about entities such as customers. The TCA Data Sharing and Security (DSS) feature allows you to define rules around who can create, update or delete customer data. For more information please refer to the Oracle Trading Community Architecture Administration Guide.
OM: Administer Public Queries
ONT_ADMINISTER_PUBLIC_QUERIES
This profile option determines which responsibility is able to create and update public queries within Order Management windows.
OM: Apply Automatic Attachments
OE_APPLY_AUTOMATIC_ATCHMT
This profile option determines whether rule-based attachments are applied without user intervention.
OM: Allow model fulfillment without configuration
ONT_ALLOW_MODEL_FULFILL_WITHOUT_CONFIG
In order to enable you to progress model lines which do not have child lines attached, the profile option OM: Allow Model Fulfillment without Configuration has been introduced. When you set this profile option to Yes, you are allowed to progress the model line and not wait at fulfillment any longer, even if you do not have a child line attached to it. If you set this profile option to No, which is the default value, the current functionality will be carried out: the model line will get fulfilled only if it does not have any child lines attached to it. If the model line is not configured, i.e. if it does not have any child lines attached to it, then the model line waits at fulfillment thus giving the user a chance to configure the model.
OM: Assign New Set For Each Line
ONT_CHECK_WAIT_TO_FULFILL_LINE
The default is set to “N” which creating ONE Ship/Arrival Set per order. Set to 'Y' which creates a separate ship/arrival set per line, resulting in enforcing that each line is shipped complete.
OM: Authorized to Override ATP
ONT_OVERRIDE_ATP
This profile option controls which responsibilities or users have the authority to perform the ATP override. If YES, then the user or responsibility can override the ATP Schedule Date. Null is interpreted as No. This can be set at the site, responsibility, or user level.
OM: Automatically Interface Lines to IB on Fulfillment
ONT_AUTO_INTERFACE_LINES_TO_IB
This profile option enables you to control the interfacing of non-shippable items to Install Base (IB). The default value is Yes and if you have not set any value for this profile, then the application assumes the value to be Yes. The value Yes ensures that all non-shippable lines that reach fulfillment are automatically interfaced to IB. If you set No as the value, then the non-shippable items are not interfaced to IB automatically.
OM: Automatically Open Related Items Window
ONT_OPEN_RELATED_ITEMS
This profile option allows the user who does high volume up-selling and cross-selling to have the Related Items window open automatically for all items which have relationships defined. Options are Yes or No (default).
OM: Auto Push Group Date
ONT_AUTO_PUSH_GRP_DATE
This profile option controls scheduling when a new line is inserted into an existing set. If the new line cannot be scheduled on the same date as the rest of the set, this profile is used. Select from:
Yes: The entire set will be automatically rescheduled.
No or NULL: An error will occur. You can change the dates or quantities to make scheduling succeed.
This profile option can be overridden for a parameter specific to customers or customer sites by setting a value in the Customer window.
The default is NULL.
OM: AutoSchedule
ONT_AUTOSCHEDULE
This profile option determines the default setting for autoscheduling orders, and also controls the display of the Availability window within the Sales Order Lines window. Please note that autoscheduling orders is only supported for orders that contain standard line items, not models or kits.
Select from:
Yes: Order lines are scheduled automatically at the time of entry. Automatically display the Availability window within the Sales Order window when entering order line details.
No or NULL: Order lines are not scheduled automatically at the time of entry. Does not automatically display the Availability window within the Sales Order window when entering order line details.
Note: If the item or model is a standard item or has the item ATP flag enabled, ATP inquiry will automatically be performed on the item or model once it has been entered on an order line and a user exits the item field.
The Line Generic workflow process sequences the line scheduling action to occur after you book the order. However, even if you have set this profile option to No and you indicate ship set or arrival set on a order line, the order entry processing schedules the line and sets the Visible Demand Flag.
To group lines into ship sets and arrival sets, order entry processing uses the warehouse, scheduled shipment date, ship to location, shipment priority, and shipment method. Therefore, it schedules the order lines with ship set values to obtain scheduled shipment date.
If you want the Line Generic workflow process to schedule an order line, you cannot specify a ship set or arrival set for it.
OM: Cascade Service
ONT_CASCADE_SERVICE
If set to No, services will not be automatically cascaded from model to its options. When a service is added to a model,
depending on the profile value the application will or will not automatically cascade the service to the options.
OM: Change SO Response Required
This profile option determines if a response is required to an outbound Change SO XML message. If a response is required, the order is put on hold until a response is received from the customer.
OM: Charges for Backorders
This profile option controls the setting of the Calculate Price Flag when backorder lines are created.
Select from:
No or NULL: The Calculate Price Flag will be set to Freeze, and the pricing engine will not apply charges. Yes: The Calculate Price Flag will be set to Partial to enable charges to be calculated when the backordered item ultimately ships.
OM: Charges for included item
ONT_CHARGES_FOR_INCLUDED_ITEM
This profile option determines if Order Management will calculate and return charges for included items. The profile option setting does not control the pricing of included items, only the calculation and return of charges associated with an order line containing an included item.
Select from:
Yes: Calculate and return charges for included items.
No: Do not calculate charges for included items.
OM: Charging Privilege
OE_CHARGING_PRIVILEGE
This profile option controls your ability to manually apply freight and special charges on an order or order line.
Select from:
Full Access: You can modify and apply charges, but you cannot modify non-overridable charges.
View Only Access: You can only view charges.
Unlimited Access: You can modify and apply all charges including the non-overridable charges.
OM: Configuration Quick Save
ONT_CONFIG_QUICK_SAVE
This profile option determines how Order Management will save option or model class lines for unbooked sales orders from within the Sales Order window only.
If you set this profile option to Y, class lines will be saved by a direct database insert call with a minimum of order line defaulting values, unless the value of the Order Management profile option OM: Included Item Freeze Method is set to Entry. If the value of OM: Included Item Freeze Method is set to Entry, you cannot perform direct database inserts of model or class order lines with a minimum of defaulting.
OE: Commitment Balance Checking
OE_COMMITMENT_BAL_CHECK
This profile option is obsolete and no longer used by Order Management.
OM: Commitment Sequencing
OE_COMMITMENT_SEQUENCING
This profile option determines whether or not Oracle Order Management calculates and stores the amount of the line that can be paid using the commitment, and if commitments will be applied in Oracle Receivables in the same sequence that they are applied in Order Management. Select from:
Yes: Order Management populates the commitment applied and then will interface the applied commitment amount to Oracle Receivables.
Note: If you set this profile option to Yes, and you have not installed Bills Receivables for Oracle Receivables, Order Management will not capture the applied commitment amount and therefore will not relay commitment applied amounts to Oracle R no Warning or Error message is displayed.
No: Order Management does not calculate the exact commitment applied amount for an order line. Instead, the extended amount of the line is shown in the commitment applied field within the Sales Order Line, Pricing Tab window.
OM: Contact Center Actions Menu Name
ONT_AGENT_ACTION_PROFILE
Agent actions are defined as functions. Depending on the functions that have been mapped to menus, the corresponding associated agent actions are available from the Line Items sub-tab page. This profile option holds the name of that menu. The default value will be the value of the Order Management seeded menu ‘ONT_CONTACT_CENTER_SUB_MNU’.
OM: Context Responsibility for Upgraded Orders
OE_RESP_FOR_WF_UPGRADE
This profile option is used to flag certain responsibilities to be used when setting the applications context for deferred activities for upgraded orders and order lines. It is used for customers who are upgrading and only needs to be set if a user, who has created orders, (created_by column in Order Management schema) has multiple responsibilities that point to a single operating unit.
This profile option can only be set at the Responsibility level.
OM: Copy Model DFF to child lines.
This profile option enables copying of all flexfields to the lines from the model line. Context sensitive flexfie you may not want the same flexfields copied to all the child lines of a model. The default value is No. Set this parameter to 'Yes' in order for the values to copy.
OM: Create Account Information
ONT_CREATE_ACCOUNT_INFORMATION
This profile option is used to set the user's permissions to create accounts, sites, and contacts. It can be set at the Site, Application, Responsibility, and User levels.
The seeded profile values are:
All: The user is permitted to create Accounts, Account Sites, Account Contracts, and related information
Account Site and Account Contact Only: The user is permitted to create Account Sites, Account Contracts, and related information only
None: The user is not permitted to create any of the above
The default value is None.
The Create Account Layer API will check this profile and create the account layer only if the user has the correct permissions. The calling application can pass a profile value to the API. It is useful if the calling application has already determined the user's privileges.
OM: Credit Card Privileges
ONT_CREDIT_CARD_PRIVILEGES
This profile option is used for controlling the entry of new credit card details, updating existing details, and allowing for manual authorization. The valid values for this profile option are Yes and No. This profile option has been modified, it's previous valid values were All, Limited and None and in the previous release, this profile option would additionally be used for controlling the card number display. The masking / display function for the credit card number is now controlled from Oracle Payments. Please visit Oracle Payments Implementation Manual for more details.
OM: Cust Item Shows Matches
OE_CUST_ITEM_SHOW_MATCHES
This profile option is obsolete.
OM: Customer Service Feedback
ONT_FEEDBACK_PROFILE
This profile option indicates the Customer contact that a workflow notification will be sent to for RMA requests entered via the Order Information Portal. The values for the LOV for this profile option is all users defined to Oracle Applications via the System Administrator responsibility having no customer contacts.
The default for this profile option is Null.
OM: Customer Service Report Defect
ONT_REPORTDEFECT_PROFILE
This profile option indicates the Customer contact that will receive a workflow notification for any Report Defects submitted via the Order Information Portal. The values for the LOV for this profile option is all users defined to Oracle Applications via the System Administrator responsibility having no customer contacts.
The default for this profile option is Null.
OM: DBI Installation
ONT_DBI_INSTALLED
This profile option is used to flag whether DBI has been installed. If the profile option is set to Yes, then data is collected for DBI usage. If the profile option is set to No, then data is not collected for DBI.
OM: Debug Level
ONT_DEBUG_LEVEL
This profile option is used to store debug messages to assist in problem identification. The OM: Debug profile option controls which debug messages get written to the debug log based on their assigned level. The directory to be specified for this profile should be available in utl_file_dir parameter of the init.ora file (or check v$parameter) of the application database instance.
Assigning a value greater than 0 or NULL causes debugging to be turned on. The value of this option determines the level of debug messages printed within a log file. For example, if OM: Debug Level has a current value of 3, all debugging messages with a level of 1,2 or 3 will be spooled out to the debug log.
Valid values for this profile option are:
NULL: Do not print any debug messages
1:Level 1; Print a limited subset of debug messages (level 1)
2:Level 2; Print a limited subset of debug messages, including level 1
3:Level 3; Print a limited subset of debug messages, including levels 1,2
4:Level 4; Print a limited subset of debug messages, including levels 1,2 3
5:Level 5; Print all debug messages
If you set this profile option to a value other than NULL, system performance may be affected, because creating and updating a debug log is a task that will consume a lot of system resources as you enter higher debug levels.
Order Management recommends you set this profile option only if you are attempting to gather additional details for
unexpected application issues and then reset the value back to NULL once you have gathered the necessary debug details.
The default for this profile option is NULL.
OM: Debug Log directory
OE_DEBUG_LOG_DIRECTORY
This profile option determines the default directory used to store log file outputs when performing Order Management debugging.
OM: Default Sales Agreement Type
OE_DEFAULT_BLANKET_ORDER_TYPE
This profile is the first preference to default the transaction phase, negotiation or fulfilment on Sales Agreements. This profile should be allowed to setup only at the responsibility and site level.
OM: Default Sales Agreement Transaction Phase
ONT_DEF_BSA_TRANSACTION_PHASE
This profile to defaults the order type to generate sales agreement number. This profile should be allowed to setup only at the responsibility and site level.
OM: Default Salesrep
ONT_DEFAULT_PERSON_ID
A profile to default the dummy salesrep for the Telesales Order. The Telesales team will pass the salesrep_id for the order if that information is available in the eBusiness Center. If no salesrep is passed to the Sales Orders form, then Order Management will default the salesrep value from the profile setup in Order Management. Integration with TeleSales is available with a TeleSales license.
OM: Default Sales Transaction Phase
ONT_DEF_TRANSACTION_PHASE
A default source for the transaction phase on the Quote Sales Order. The default is null for negotiation and fulfillment.
OM: Delay Scheduling
When the value of this profile option is set to Yes, then the scheduling of a line is performed only when the changes made are committed to the database, as opposed to simply navigating out of the line record.
OM: Discounting Privilege
ONT_DISCOUNTING_PRIVILEGE
This profile option provides the choice of controlling user's ability to apply discounts on an order or order line.
Select from:
Full: Ability to apply any valid discount against an order or order line, as long as the order type of the order does not enforce list prices. (Default value).
Non-Overridable Only: Ability to apply only non-overridable discounts against an order or order line.
Unlimited: Ability to apply any valid discount against any order or order line, regardless of whether the order type of the order enforces list prices.
None: No privileges, view-only access.
Note: A Null value for this profile option is handled as if you selected the value FULL.
OM: Display Actions Button vs. Poplist
Controls whether the traditional button for Actions or a pop list will be used to display available Actions. Valid values are: Button and Pop list. The default value will be Button for backward compatibility.
OM: Display Current Selections in Pricing and Availability
ONT_PANDA_DISPLAY
Yes or No - default is No. Determines whether or not to show the saved selections section of the P&A form
OM: Display New Order After Copy
You can choose to display the newly copied order depending on the value of this profile option. If the value of the profile option is set to Yes, the box Display New Order after copy on the Copy Orders window (Quick Copy tab) will be selected and you can view an order that has been copied in the sales orders window. If the value of the profile option is set to No, the box Display New Orders after copy will be unselected and the newly copied order will not display automatically in the sales orders window, you will need to query for it. However, you can override the selection of the check box Display New Order after Copy in the Copy window while copying.
OM: Electronic Message Integration Event Sources
ONT_EM_INTEG_SOURCES
Order Sources enabled for Integration Business Event. Based on the source, you can enable the History which will be maintained for that source in the Electronic Messaging history table.
OM: E-Mail Required on New Customers
ONT_MANDATE_CUSTOMER_EMAIL
This profile option determines whether the field E-mail address is required for any customer or customer contact you define within Order Management. Select from:
Yes: E-mail address is required, for both the customer and customer contact, when defining or updating a customer or customer contact.
No or NULL (the default): E-mail address is not required when defining or updating either a customer or customer contact.
OM: Enable Group Pricing For DSP Lines
ONT_GRP_PRICE_FOR_DSP
When demand interface appends order lines to an existing order, this profile option controls whether other unchanged order lines should be sent to the Pricing Engine for repricing.
Setting this profile option to No improves demand interface performance. The default value is No.
You should only set this profile option to Yes when you want your orders created by demand interface qualify for Promotional Goods, Other Item Discounts or other line group level modifiers defined in Advanced Pricing.
OM: Enable Related Items and Manual Substitutions
ONT_OPEN_RELATED_ITEMS
Values: Yes or No
Default Value: No
Usage: This option enables you to turn on Related Items. APS users should not turn on Related Items because the forecast demand consumption