SAP Multi-Bank Connectivity MBC 的产品帮助 事务代码

/BSNAGT/ALERT检查警报
/BSNAGT/ARC_CU维护保留时间
/BSNAGT/ARC_DELETE删除已归档消息
/BSNAGT/ARC_PREP选择要归档的消息
/BSNAGT/ARC_RELOAD重新加载已归档消息
/BSNAGT/ARC_WRITE归档所选消息
/BSNAGT/CHECK_QUEUES检查 XI 队列
/BSNAGT/DELEXPALERTS删除已过期警报
/BSNAGT/DELEXPMSG删除已过期消息
/BSNAGT/DELPING删除 Ping 消息
/BSNAGT/FILE_MONI连接器监控器
/BSNAGT/FILE_MONI2测试:连接器监控器
/BSNAGT/FILE_SEND将消息发送到 FSN
/BSNAGT/INDEX_CREATE创建搜索索引
/BSNAGT/INDEX_DELETE删除搜索索引
/BSNAGT/INDEX_TEST测试搜索索引创建
/BSNAGT/LOGFSN 连接器日志
/BSNAGT/MONITOR连接器监控器
/BSNAGT/MONITOR_ADMI连接器监控器(管理)
/BSNAGT/MSG_PULL拉取 FSN 消息
/BSNAGT/MSGIDNRO维护编号范围(消息标识)
/BSNAGT/PICK_FILES文件提取
/BSNAGT/PING发送 Ping 请求
/BSNAGT/PULL_LOG拉取日志
/BSNAGT/RFCHTTP API 连接测试
/BSNAGT/SEARCH有效负载搜索
/BSNAGT/SEARCH_MSG搜索消息(无搜索索引)
/BSNAGT/SETEXPMSG检查/设置已过期消息
/BSNAGT/SETPROFILEID设置/更新 SSF 参数文件标识
/BSNAGT/TOOLSFSN 连接器工具
/BSNAGT/TRACE跟踪监控器
/BSNAGT/TRACE_DEL删除跟踪
/BSNAGT/UPLOAD_FILE手动创建财务服务网络消息

SAP Multi-Bank Connectivity

SAP Multi-Bank Connectivity is an SAP Business Technology Platform (BTP) solution managed by SAP to provide customers connectivity with their banks.

Use

Note

This guide is pre-filtered on content when your SAP Multi-Bank Connectivity tenant is deployed in the Cloud Foundry environment of the SAP Business Technology Platform. If your tenant is deployed in the Neo environment, simply choose Neo Environment up in the filter. If you don't see any filter, please choose Show Filter in the action bar. You can switch between the two types of documentation anywhere in the document.

SAP Multi-Bank Connectivity is based on integration services deployed in BTP that enable the integration of business processes spanning different departments, organizations, or companies.

For the integration between the customer's SAP system and SAP Multi-Bank Connectivity, the connector for SAP Multi-Bank Connectivity is utilized. All messages to and from SAP Multi-Bank Connectivity pass through the connector. Message monitoring is available at the connector for SAP Multi-Bank Connectivity using either the classical Connector Monitor (/BSNAGT/MONITOR, for releases before SAP S/4HANA 1909 FP01) or the Manage Bank Messages SAP Fiori app (starting at SAP S/4HANA 1909 FP01 or SAP S/4HANA Cloud). Each message sent through the connector for SAP Multi-Bank Connectivity has a sender ID, receiver ID, message type, file name, message content, as well as other context information, such as SWIFT parameters or approval user information required for the integration towards the banks.

Features

SAP Multi-Bank Connectivity supports the exchange of all types of messages. The most relevant sources of messages are automated, but other sources and message types can also be sent to the cloud service or can be received.

Outbound Messages from SAP System to Bank

The available integration scenarios for outbound communication are as follows:

  • Payments from:

    • Payment Run

    • FI-CA

    • Employee Central Payroll (ECP)

    • Advanced payment management

  • Treasury confirmations

  • Generic file pickup

When the settings of the payment format indicate to send the message to SAP Multi-Bank Connectivity, no physical payment file is created. Instead a message is created within the connector for SAP Multi-Bank Connectivity. This message includes the payment format content. After connectivity between the connector and SAP Multi-Bank Connectivity has been established, the message is immediately sent from the connector to SAP Multi-Bank Connectivity and then on to the bank.

For more information, see Outbound Payment Processing.

Inbound Messages from Bank to SAP Customer

Since SAP Multi-Bank Connectivity is closely integrated with the SAP back-end system, it can seamlessly update various other modules in the SAP system once the messages are available from the banks.

The process is as follows:

  • The Pull Messages report running as a scheduled job (/BSNAGT/MESSAGES_PULL) pulls messages from SAP Multi-Bank Connectivity.

  • The message is processed by the respective business process triggered by the connector for SAP Multi-Bank Connectivity based on the message type.

Based on the message type, the system either triggers automatic processing or triggers a download to a file directory or sets the status of the message to indicate that manual processing is required.

Supported processes for automated processing include the following:

  • Payments

    • Payment messages (all formats)

    • Status messages

    • Intraday statements

    • End of day statement

    • Lockbox

  • Confirmations

    • MT300 /MT320

  • Bank fee reports

    • Bank Service billing

For more information, please see Inbound Message Processing.

All other processes are for manual processing in the connector for SAP Multi-Bank Connectivity.

For upcoming features, see the SAP Road Map Explorer​编辑 for SAP Multi-Bank Connectivity.

内容概要:本文详细探讨了双馈风力发电机(DFIG)在Simulink环境下的建模方法及其在不同风速条件下的电流电压波形特征。首先介绍了DFIG的基本原理,即定子直接接入电网,转子通过双向变流器连接电网的特点。接着阐述了Simulink模型的具体搭建步骤,包括风力机模型、传动系统模型、DFIG本体模型和变流器模型的建立。文中强调了变流器控制算法的重要性,特别是在应对风速变化时,通过实时调整转子侧的电压和电流,确保电流和电压波形的良好特性。此外,文章还讨论了模型中的关键技术和挑战,如转子电流环控制策略、低电压穿越性能、直流母线电压脉动等问题,并提供了具体的解决方案和技术细节。最终,通过对故障工况的仿真测试,验证了所建模型的有效性和优越性。 适用人群:从事风力发电研究的技术人员、高校相关专业师生、对电力电子控制系统感兴趣的工程技术人员。 使用场景及目标:适用于希望深入了解DFIG工作原理、掌握Simulink建模技能的研究人员;旨在帮助读者理解DFIG在不同风速条件下的动态响应机制,为优化风力发电系统的控制策略提供理论依据和技术支持。 其他说明:文章不仅提供了详细的理论解释,还附有大量Matlab/Simulink代码片段,便于读者进行实践操作。同时,针对一些常见问题给出了实用的调试技巧,有助于提高仿真的准确性和可靠性。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

SAP爱好者

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付:¥1
获取中
扫码支付

您的余额不足,请更换扫码支付或充值

打赏作者

实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值