Ariba-Administrative Email Notifications

 

Members of customer administrator groups can manage the list of recipients that receive administrative email notifications based on their group memberships and user roles.

Notifications related to:	Notification Name	Notification Description
Customer Catalogs	Catalog Note Expiry	Notifies recipients of the approaching expiry of the Note pane content on the customer catalog home page.
	Inactive Items in Kit	Notifies recipients of inactive items in a customer catalog kit.
	Supplier Data Import Failure	Notifies recipients of errors encountered during import of a supplier customer catalog or a type definition file.
	Unknown Catalog Supplier	Notifies recipients that the supplier associated with an imported customer catalog subscription isn't defined in your site configuration.
	Unknown Catalog Supplier Resolution	Notifies recipients that an issue of a supplier associated with an imported customer catalog subscription who wasn't configured in your site has been resolved.
	Unknown Catalog Supplier Resolution Overdue	Notifies recipients that the resolution of an issue of a supplier associated with an imported customer catalog subscription who wasn't configured in your site is overdue.
Collaboration Documents	Collaboration Proposal Submission	Notifies recipients of the supplier's proposal in response to a collaboration request.
	Collaboration Proposal Withdrawal	Notifies recipients of the supplier's withdrawal of a previously submitted proposal.
	Collaboration Request Cancellation	Notifies recipients of cancellation of a collaboration request.
	Collaboration Request Declination	Notifies recipients of the supplier's declination of a collaboration request.
	Collaboration Request Message	Notifies recipients of a new message from the supplier or a collaboration team member on the collaboration request's message board.
	Collaboration Request Routing Failure	Notifies recipients of the failure of transmission of a collaboration request to the supplier via Ariba Network.
	Contractor Survey	Notifies recipients of a contractor survey that needs to be completed.
	Expense Sheet Import Error	Notifies recipients of the errors during import of expense sheets.
	Expense Sheet Routing Failure	Notifies recipients of the failure of transmission of expense sheets to Ariba Network.
	Change Order Collaboration Request Cancellation	Notifies recipients of cancellation of the collaborative change order request.
	Timesheet Import Error	Notifies recipients of errors encountered during import of a time sheet.
	Timesheet Routing Failure	Notifies recipients of the failure of transmission of a time sheet to the supplier via Ariba Network.
Contracts	Automatic Withdrawal of Release Order	Notifies recipients of automatic withdrawal of release orders due to changes to the associated contract.
	Catalog Subscription Activation Failure	Notifies recipients of errors encountered during activation of a customer catalog subscription generated from a contract.
	Catalog Subscription Deactivation Failure	Notifies recipients of errors encountered during deactivation of a customer catalog subscription generated from a contract.
	Catalog Subscription Load Failure	Notifies recipients of errors encountered during loading of a customer catalog subscription generated from a contract.
	Contract Approaching Expiration	Notifies recipients of the number of days after which a contract will expire.
	Contract Approaching Limit	Notifies recipients that the maximum commitment amount of a contract has reached a specified percentage of its limit.
	Contract Closure	Notifies recipients of the closure of a contract.
	Contract Minimum Commitment Not Met	Notifies recipients that the minimum commitment hasn't been met and that the expiration date of the contract is approaching.
	Contract Opened	Notifies recipients of a contract that has been opened.
	Evergreen Contract	Notifies recipients of the approaching notification date of an evergreen contract.
	Parent Contract Closure	Notifies recipients of the closure of a parent contract associated with a sub-agreement.
	Parent Contract Opened	Notifies recipients of a subagreement's parent contract that has been opened.
Integration Events	Integration Event Aborted	Notifies recipients an Integration Event is aborted.
	Integration Event Complete	Notifies recipients of the completion of an Integration Event.
	Integration Event Complete with warning	Notifies recipients of the completion with warning of an Integration Event.
	Integration Event Error	Notifies recipients an Integration Event has some error.
	Integration Event InProcess	Notifies recipients an Integration Event is in process.
	Integration Event Not Run	Notifies recipients an Integration Event isn't run.
	Integration Event Pending	Notifies recipients an Integration Event is in pending.
Invoices and Invoice Reconciliations	Ariba Network Invoice Loader Errors	Notifies recipients of errors while loading cXML invoices from Ariba Network.
	Correction Letter Received for Invoice	Notifies recipients of a correction letter sent by the supplier for an invoice.
	Invoice Reconciliation Push Failure	Notifies recipients of failure during transmission of invoice reconciliation to the external system.
	Invoice Reconciliation Rejection	Notifies recipients of the rejection of an invoice reconciliation (IR) document.
	Invoice Reconciliation Send Failure	Notifies recipients of the failure of transmission of an invoice reconciliation document's copy to Ariba Network.
	Invoice Send Failure	Notifies recipients of the failure of transmission of a copy invoice to Ariba Network.
Milestone Trackers	Milestone Verification and Approval	Notifies recipients of the verification and approval of a milestone tracker by an approver.
Payments	Errors in Advance Payment Export to ERP	Notifies recipients of errors during export of advance payment documents to external systems.
	Payment Send Failure	Notifies recipients that a payment request or payment transaction can't be sent using the designated payment send method.
	Skipped Payment Request	Notifies recipients of the failure of transmission of a payment request to the supplier via Ariba Network.
Purchasing Cards	Charge Reconciliation Approval	Notifies recipients of the approval of a charge reconciliation document.
	New PCard Charges	Notifies recipients of new charges on their corporate PCards.
	Overdue PCard Charges	Notifies recipients of overdue pcard charges that must be reconciled.
	PCard Charge Rejection	Notifies recipients of the rejection of a purchasing card charge reconciliation (PCCR) document.
	Updated PCard Charges	Notifies recipients of a PCard charge that has been updated.
Receipts and Service Sheets	Copy Receipt Loader Errors	Notifies recipients of errors during loading of receipts.
	Order Fully Received	Notifies recipients that an order has been fully received.
	Order Received	Notifies recipients that items from an order have been received.
	Receipt Push Failure	Notifies recipients of the failure of transmission of a receipt to the external ERP system.
	Rejection of Shipped Items	Notifies recipients of the rejection of a shipped item by a user.
	Service Sheet External System Error	Notifies recipients of errors encountered while sending service sheets to external system.
	Service Sheet Validation Error	Notifies recipients of validation errors in imported service sheets.
Requisitions and Orders	Attachments Omitted from Orders	Notifies recipients of attachments that have been omitted due to file size limitations from purchase orders sent to Ariba Network .
	Bulk Order Closure Failure	Notifies recipients of failure of the request for bulk closure of purchase orders.
	Change or Cancellation of Manual Order	Notifies recipients of a manual order that has been changed or cancelled.
	Copy Order Loader Errors	Notifies recipients of errors during loading of copy orders.
	Generation of Manual Order	Notifies recipients of the generation of a manual order.
	Held Line Items Cancellation	Notifies recipients of cancellation of held line item by a purchasing agent from the purchasing workbench.
	Held Line Items Pending Aggregation	Notifies recipients of held line items that are pending aggregation.
	Immediate Order Transmission Failure	Notifies recipients of the immediate transmission failure of an order to Ariba Network and the external ERP system.
	Order Confirmation Received	Notifies recipients of an order confirmation message received for a purchase order.
	Order Confirmation UOM Error	Notifies recipients that the unit of measure in an order confirmation message is different from the unit of measure in the associated purchase order.
	Permanent Order Rejection From Ariba Network	Notifies recipients that a purchase order has failed to be routed to Ariba Network even after the specified maximum number of retries.
	Purchase Order Cancellation Disabled	Notifies recipients that sending of cancel orders to ERP systems has been disabled for their site.
	Purchase Order Change Disabled	Notifies recipients that sending of change orders to ERP systems has been disabled for their site.
	Purchase Order ERP Push Error	Notifies recipients of the failure of transmission of an order to the external ERP system.
	Receival of Pricing terms for Requisitions	Notifies recipients that pricing terms have been received for a requisition.
	Requisition Automatically Withdrawn	Notifies recipients that a requisition has been automatically withdrawn because the associated order couldn't be sent to the external system.
	Requisition Import Error	Notifies recipients of the errors encountered during requisition import.
	Ship Notice Error	Notifies recipients of errors encountered during processing of a ship notice.
	Ship Notice Received	Notifies recipients of a ship notice that has been received for a purchase order.
	Submitted Requisition Budget Check Failure	Notifies recipients that a submitted requisition has failed budget check in the external ERP system.
Other scenarios	Approval Queue Operation Failure	Notifies recipients of errors when processing approval queue operations
	Reassigned Approvable Roles	Notifies recipients of one or more approvable roles that have been reassigned.
	Unknown Supplier	Notifies recipients that the supplier associated with an imported approvable isn't defined in your site configuration.
	Unknown Supplier Resolution	Notifies recipients that an issue of a supplier associated with an imported approvable who wasn't configured in your site has been resolved.
	Unknown Supplier Resolution Overdue	Notifies recipients that the resolution of an issue of a supplier associated with an imported approvable (who wasn't configured in your site) is overdue.

出處來源：https://help.sap.com/docs/buying-invoicing/notifications-reference-guide/list-of-administrative-email-notifications

Ariba-Email Notification

 

Best Practices for Avoiding Delayed or Failed Email Notifications

Use these guidelines to avoid delayed or failed email notifications from SAP Ariba Procurement solutions.

The more email addresses assigned to an approvable document notification, the more likely a delay or failure of an email notification. To avoid delayed or failed email notifications, do the following:

• Use distribution lists for email notifications, instead of groups or individual email addresses. You can add a new distribution list or remove a distribution list, and users can be removed from a list by their organization's administrator.
• Remove email addresses from the list of recipients, if needed. This does not remove a user from a group, it removes the user from receiving any email notification for any approvable document.
• Allow users to manage which notifications they receive. If users can't opt out of receiving notifications, they'll continually be sent notifications based on group membership.

For more information on distribution lists, removing email recipients, and allowing users to manage notifications, see Managing Email Notification Settings and Recipients.

• Encourage users to receive email notifications as a consolidated email message, instead of individual notifications. Consolidated notifications reduce the number of emails sent. Notification preferences are based on the approvable document type and the user's role: approver or watcher. Use the Default Notification Preferences task in Ariba Administrator. The following figure displays notification preferences for receipts, as an approver, the notification is set to Send consolidated email.

來源出處

Ariba-requester and preparer

 

在Airba的世界有requester 及 Preparer 二種人，Preparer是指開Ariba單子的人，而Requester就是指Ariba單子上的 On behalf of 這個欄位的人

This document uses the following terms when describing users who receive email notification messages:

• A preparer is the person who fills out or submits a request.
• A requester is the user on whose behalf the request is submitted. Often the requester and preparer are the same, but not always. For example, if a personal assistant fills out all requisitions for the Technical Publications Manager, then the assistant is the preparer and the Technical Publications Manager is the requester.
• An approver is a required approver. Required approvers must either approve or deny the request.
• A watcher is an optional approver who is notified of changes in approval flow, but doesn't have to act.

Ariba-Transport request For CIG

Ariba CIG 的Addon 放在 S/4 后，部份的SPRO設定不會自動產生TR，可以籍由 SM30，輸入ARBCIG_TVARV去產生TR 也可以依如下的方式去產生TR傳到對應的Client，這二個是同樣的方式。

Transport Parameters and Filters

Use

This is to create transport request to transfer parameters and filters of the ARBCIG_TVARV table across SAP ERP or SAP S/4HANA instances.

Requirements

The entries required for integration SAP Ariba solutions have already been maintained and these entries need to be transported to other SAP instances.

Activities

1. On click of IMG Activity. Change View "TVARV generalized for fields": Overview screen appears.

2. Click Table View -> Transport.

3. Create or select an existing transport request to save the parameters and filters.

4. Select the parameters and the filters that need to be transported.

5. Click Include Request to add the selected parameters and filters to the transport request that was created/selected.

6. Click Save.

參考來源：

https://help.sap.com/docs/sisgw/sap-ariba-cloud-integration-gateway-installation-guide/transferring-data-across-sap-erp-and-s-4hana-system-landscapes

Ariba-Invoice上的charge 不會自動從PO上帶過來

在Ariba B&I Solution中，PO上可以輸入Charge，例如Shipping Charge或是Handling Charge，這些Charge在B&I開立Invoice時，會自動帶到Invoice上，不過預設金額會是放0

某程度可以視為PR/PO上的Charge是預估值，但是Invoice上的是實際值，來看待這個系統行為

Ariba-Intelligent Configuration Manager(ICM)

 

在Ariba的ICM中，可以自訂某些參數，讓某些流程可以依此參數變更。

Application.Mobile.EnableReceivingForMobile，例如起用此參數就可以在Mobile APP上進行收貨的動作

參考Link：

https://help.sap.com/docs/buying-invoicing/intelligent-configuration-manager-parameters-reference/intelligent-configuration-manager-parameters-reference

Ariba-預設Group Payment Agent

荒廢好久了的網站....這段期間做了S/4的昇級，也導了SAC，也做了SF及Ariba，就從Ariba開始來更新一下自己的網頁吧～

查詢問題時，只要用戶有 Payment Agent 這個 Group，用戶可以查到同一個 Purchase Unit 下的Invoice，

另外在 Manage 下

1.Approvable Role Assignments 這個功能是掛 Reassign Charge 這個 Role 下

2.Reconcile Charges 及 Unassigned Charges 是掛在 Charge Users 這個 Role 下

3.Reconcile invoice 是掛在 Payment agent 這個 Role 下

摘要自如下
https://help.sap.com/docs/buying-invoicing/sap-ariba-procurement-solutions-group-descriptions/additional-information-about-groups?q=default+group#loio6bce3a8ec1da1014a04b89615ddb64f4

Ariba 的 Mobile APP 不支援 Invoice 作業....

Ariba-的那些事

荒廢好久了的網站....這段期間做了S/4的昇級，也導了SAC，也做了SF及Ariba，就從Ariba開始來更新一下自己的網頁吧～

圖：取自網路

Ariba 這公司及產品是在 1996 年開發問巿的，後來在 2012 年被 SAP 併購。所以日后大家都慣稱 SAP Ariba這條產品線。 

SAP Ariba 是 SAP 的一套公有雲產品(Sourcing to Pay)，可以概略區分為上游模組(如合約管理、供應商管理、供應商評鑑....)及下游模組(Buying、Invoice....)，下游模組也可以概念性的說成Procurement To Pay的流程，所以含括了PR、PO、GR、INV....等等行為。因為是公有雲所以要客制的話都要找 SAP 原廠提出 CRD 進行客制評估。

Ariba 也有含括供應商平台，官方現在簡稱為SBN(SAP Business Network)，其實就是過往Ariba業介大家熟悉的簡稱Ariba Network，基本上一個AN平台上每家公司會對應一個或多個ANID，這個ANID也概分為企業級版本或是標準版本，標準版本是不用收費的。

SBN是供應商來收發和客戶間交易的一個處理平台，如交期答交、發票輸入...等等。在國外大型公司甚至會將SBN上的這些功能和自家的ERP進行串接。Ariba 的串接ERP對像，並不限制在SAP的ERP上，甚至听我的顧問提及 Ariba 原始設計是針對Oracle 的ERP做為介接對像的，所以其提供了Web Service 可以使用；而和SAP 自家ERP的整合只能說....需要持續的完善。

MM-34 Scheduling aggrement

1.Scheduling agreement
	使用scheduling agreement 效益： 1.可以降低開出大量的PO及contract release order，因為是在同一個scheduling agreement下展出新的scheduling line 2.公司庫存量會較低，幾乎由供應商依排定需求JIT送達 3. scheduling agreement是一個長效合約，可以談到較佳的條件 Scheduling agreement 一定是和工廠相關的，所以item cate.W及M不能用，若item cate.是使用subcontract的話就可以維護下階料
1.1 Automatic Scheduling Agreement Schedule Lines
	SA的schedule line可以經由MRP(planning run)產生，需符合如下條件 存在source list/物料主檔的procument type要設為F/planning run的schedule line 參數要設定2或3
1.2 Firm and Trade-Off Zones
	The firm and trade-off zones決定了取消delivery schedule 時要承擔的成本 Firm zone (production go-ahead period) 若取消或是修正交貨期間會被供應商收取生產及物料成本；也就你已確認貨要在此段日期交貨 Trade-off zone (material go-ahead period) 若取消或是修正交貨期間會被供應商收取物料成本；也就你已計劃貨要在此段日期交貨 Firm and Trade-Off Zones是用日曆日計算也就是含六日 All schedule lines with delivery dates lying beyond the firm and trade-off zones (that is, relatively far in the future) fall within the planning zone.
	The firm and trade-off zones維護在additional data中
1.3 SA type
	SA的TYPE會決定是否要做release document，有release document 的好處是你會有送給vendor delivery schedule 的記錄
	SA TYPE LP因沒有release document 所以應要設計存檔時就將資料丟給vendor SA TYPE LPA因有release document 所以這個SA的資訊是內部使用的，當產生了release document(FRC/JIT)時才會將資訊FRC/JIT的資訊給供應商
1.4 scheduling agreement (SA) release
	有二類的SA release一個是FRC一個是JIT Forecast (FRC) delivery schedules用於通知供應商中短期的需求，通常是用日或週計算 Just-in-Time (JIT) delivery schedules 用於通知供應商短期或是即時的需求，通常是用日或小時計，Planning run產生的SA schedule line 不能產生依小時計算的
	有SA release document的話，可以借由release document 找出寄給供應商何種資訊，亦可讓供應商回饋明確的交貨日期
	先建SA，再在SA補輸入 schedule line，然后再做release document
1.5 SA的資料來源
	物料主檔上的JIT若沒有被設定，也不能在SA上手動勾起來 release creation profile若沒有在供應商主檔上指定亦可以在SA上指定
	release creation profile是用來定義多常的頻率將release document提供給供應商，因為release doc.有二種FRC及JIT，所以可以用來定義此二種文件的時間區間 SA有不同的ITEM，每個item有自己的Schedule line，release creation profile會去定義后續的release doc. 應用多常的頻率(天/週)將不同的schedule line 的數量加總起來 release creation profile也可以定義向供應商提供資料的頻率
1.6 FRC/JIT的使用時機
	若SA的delivery schedule line 是含括數月，可以設定為前10天不總計數量，第11-30天每日總計數量，第30天后，by月總計數量 FRC/JIT可以同時並用，如SA的delivery schedule line 是含括數月，FRC負責處理超過tolerance的事件，而JIT則處理原本的排程；如JIT可以設定前7天不總計數量，第8至第10天每日總計，而FRC則是設定第7天到第100天依週總計
1.7 Tolerance Limits for Scheduling Agreement Items
	在release的creation profile中可以指定tolerance check的方式 FRC及JIT都可以設定上下界，超過此需求量的上下界才可以新產生一個新的schedule line；如JIT上界為2%，若原需求量100，因故需求量變更為103時(超過2%)，才會再長出一個新的schedule line
	Tolerance check只能設定在最多三種區間中
1.8 Status of SA release doc.
	Release doc. 可以用灯號去判別狀態
	若release doc. Type 同時存在FRC/JIT則灯號會依JIT為準

MM-33 contract

1.outline agreement
	Outline agreement 可分為Contract及scheduling agreement Schudling agreement可視為plant-specific contract Outline agreement通常是指針對特定的物料或是服務有事先定義好的總數量及總金額；但其上面不會有指定的出貨日及數量 通常outline agreement 會被contract release order 或是delivery schedule 給參考，這二個上面就會有指定日期及交貨數量
	就contract 及scheduling agreement 而言有二個主要的差異文件數量及物料規劃上 文件差異方面contract 可以接很多個contract release order 但是scheduling agreement 后面只會接一個文件，后續會在此份文件上產生多筆 schedule line 物料規劃上面在planning run之后contract可以變成PR的Source supply，然后后續再轉成contract release order；而scheduling agreement 則可以在planning run后直接產生schedule line，不用再透過PR或是plan order 去轉
2.contract
	Contract 的release order 可以是PR/RFQ/Contract/PO Contract上的item cate.會影响欄位的畫面指派 若是庫存型料號相關acct. assignment 會從物料主檔上帶下來，若是消耗型物料會從acct. assignment 上去指定；若acct. assignment 是U則后續的contract release order 就一定要指定acct. assignment Contract 的agreement type會決定是否更新數量或是金額
2.1 contract type
	Contract 有三類數量合約(MK)/金額合約(WK)/ Distributed contracts 數量合約在表頭會記錄時間，數量控制則在item，金額對此合約不是必要的 金額合約在表頭會記錄時間，總金額控制也是表頭，但是后續的contract release order的item一定要在contract中 Distributed contract是指跨其他SAP系統的合約，其是用ale做跨系統連線
2.2 Contracts for Material Group
	Contract 有二個特別的item cate. Material unknow(M)及material group(K)，這二個item cate.都可以不用輸入料號 M主要是用在相似的物料但相同的金額上，而W則是用在不同的物料且不同的金額上
2.3 Centrally Agreed and Plant Contracts
	Contract不一定要指定plant，若有指定到plant代表此合約只對此plant生效，但是contract release order 一定要有plant
	Distributed contract(Centrally agreed contracts)可以by receiving plant 設定condition要去功能表的edit=>plant condition 下(因為不同的工廠是有可能有不同的運輸成本) 不同的receiving Plant也有可能有不同的patner