Model Distribution Problem in BD64

Hello everybody,
I'm not sure if this is the correct forum for this question, the problem that I have is as follows, I'm configuring the Model Distribution for an AUDIT Idoc, the Idocs are transfered from one system to another via SAP XI, now the problem is that for company politics every Idoc needs to go via SAP XI, even when Idoc's are transfered to the same system, and here is where I'm having the problem cause the scenario is as follows:
R/3_1 -> XI -> R/3_1,
with this scenario R/3 needs to distribute the AUDIT Idocs so XI will have the acknowledgment of the Idoc, but in BD64 in R/3 I can't generate a distribution model where the sender and the receiver system are the same, cause is the same client, any suggestions and help would be really appreciated thanks in advance.
Regards,
Julio Cesar

Hi Julio Cesar Ruiz,
in distribution module why u have create receiver system is R-3 I think first you have send IDOC to SAP XI then again come to R-3 so in this case receiver system is SAP XI
Thanks
Amit Shivhare

Similar Messages

HR ALE org model distribution - multiple business partners created

Hi,
I am experiencing weird problems with HR ALE org model distribution to CRM 7.01. It creates multiple business partners for some org units and some persons. However, it does not create them everyone. Right now it seems like a new business partner is created on every second destribution in update mode. Does anyone have an idea what might be wrong? In my understanding no new business partners should be created, rather the existing ones should be recognized and updated.
There is just one IDoc warning saying there was an error calling function module BUPR_EMPLO_ADDR_ADD because parameter value IV_X_SAVE has changed. This warning apperas everytime, also when no new business partner is created. Thus I am not sure if this is important. Also I do not use any custom coding, so I don't think that I am causing this warning.
Thanks a lot
AP
Edited by: linex83 on Mar 26, 2010 10:45 AM
Edited by: linex83 on Mar 26, 2010 10:46 AM

I just discovered a part of the problem. In CRM the relationship between the organisation unit and its business partner gets deleted if it already exists. On next update a new business partner is created, because there is no business partner assigned to the organisation unit yet.
It would be interesting to know why the relationship is deleted. Also I am not sure that it happens to all organisation units. Furthermore the same problem exists for persons.

ALE Error in BD64 while partner generation and model distribution

Dear all,
My scenario is as follows.
Transfer MATMAS from TTP105 to TTP100 system.
The steps I followed so far are as below.
On the Sender system TTP105
----

1) BD54 - Created the logical systems for sender & receiver (TTP100 and TTP105)
2) SM59 - Created the RFC destinations (TTP100 and TTP105) for both the sender and the receiver and checked the connections. They are working perfectly.
3) WE21 - Created the sender port as TTP100 (to represent that it points to the receiver system). The Type is USER and the Agent is my userid. Nothing in the outbound and inbound parameters sections.
4) BD64 - Created a modelview with the sender system as TTP105 and the Receiver system as TTP100 and the message type MATMAS. No filters defined. Saved it.
The problem begins here...
Problem#1
When I chose the created modelview and then choose Environment->Generate Partner Profiles.. I'm getting the message as No messages have been defined for the selection conditions in the model 
Can anyone guess why this error is occuring?
Problem#2
When I chose the created modelview and then choose Edit->ModelView->Distribute, again I'm getting another error which is as below.

RFC destination for synchronous communication (message type SYNCH)
Partner profile LS TTP100 SYNCH does not exist

Has anyone encountered such error message before? If yes, then please respond and rewards guaranteed for sure.
Cheers,
Sam

Thanks Ashwini for the reply. The issue was not saving as I had already saved it.
I actually solved this in another way.
The issue was in SCC4, the client 105 sender which was supposed to be assigned to my logical system had been changed by someone else to another. This was creating the whole issue.
I started all over from the scratch and found out the mistake at that step. Now everything is working fine.
Thanks for your help too!
Cheers,
Sam

Error in BD64 while partner generation and model distribution

Dear all,
My scenario is as follows.
Transfer MATMAS from TTP105 to TTP100 system.
The steps I followed so far are as below.
On the Sender system TTP105
----

1) BD54 - Created the logical systems for sender & receiver (TTP100 and TTP105)
2) SM59 - Created the RFC destinations (TTP100 and TTP105) for both the sender and the receiver and checked the connections. They are working perfectly.
3) WE21 - Created the sender port as TTP100 (to represent that it points to the receiver system). The Type is USER and the Agent is my userid. Nothing in the outbound and inbound parameters sections.
4) BD64 - Created a modelview with the sender system as TTP105 and the Receiver system as TTP100 and the message type MATMAS. No filters defined. Saved it.
The problem begins here...
Problem#1
When I chose the created modelview and then choose Environment->Generate Partner Profiles.. I'm getting the message as No messages have been defined for the selection conditions in the model 
Can anyone guess why this error is occuring?
Problem#2
When I chose the created modelview and then choose Edit->ModelView->Distribute, again I'm getting another error which is as below.

RFC destination for synchronous communication (message type SYNCH)
Partner profile LS TTP100 SYNCH does not exist

Has anyone encountered such error message before? If yes, then please respond and rewards guaranteed for sure.
Cheers,
Sam

1. There is not need to create an RFC destination for the sender system
2. If the receiver logical system and rfc destination have the same name, then there is no need to create ports, they are created automatically with the 'generate partner profiles'
3. Try saving your data before going to 'Generate Partner Profiles'
4. Problem#2 is caused because the step for Problem#1 did not execute successfully
Message was edited by:
 Kris Donald

Transaction BD64 model distribution

Hello
I've made a refresh of the QA environment, and now I have to distribute a model in transaction BD64. This distribution is necessary because the Solution Manager environment controls the users in DEV and QA environment and because the refreh we need to distribute again this model through BD64.
Does anyone knows how can I distribute this model by Solman and transaction BD64?
Regards

Hi Sridhar
To select specific employees to CRM during initial load, you must fill the Object Parameter in PFAL transaction with only the specific Employee IDs that you need.
In BD64, you can especify inside de Distribution Model, some objects to filter the data you will send periodically, but this filters are not specific fields, but infotypes, Subtype, Object. Also you can add objects to filter by others fields with a BADI.
I recommend you, to read the Application help in PFAL transaction.
Regards
Edith

Add a message type to a Distribution model dynamically (similar to BD64)

Hello,
I have a req. to add a message type to a dist. model at runtime & generate partner profiles for the same.
Are there any FM, Classes available which will help me in achieving this func.?
BR,
Suhas

Perhaps you need to re-think why you need to describe the process at one point as "Import" (from within the application) and at another as "Open" (in the Finder).
If it's "Import", that is, your application is *not* associated by default with the data, you could try and force it into the "Open With" list. I'm not sure how that would work out though, if there is no default 'open' action.
If it's "Open" you can use the standard way of associating document types with applications.

Model distribution not possible in 4.7

Hello,
We have refreshed QAS client with client copy (data) from PRD system.
Afterwards, we created ALE model (BD64) in QAS and when we try to distribute it to DEV system we get an error:
"Client XXX is not available. Please choose an existing client".
If we create model in DEV, distribution to QAS works, but after finishing model setup, sending idocs from QAS to DEV fails with the same error:
"Client XXX is not available. Please choose an existing client".
In dev_rfc logs we can only see the same message:
**** Trace file opened at 20150126 122009 CET SAP-REL 640,0,155 RFC-VER 3 865711
======> Client XXX is not available. Please choose an existing client
ABAP Programm: SAPLBD22 (Transaction: BD64)
Called function module: MODEL_VIEW_REPLICATE
User: ALEUSER (Client: XXX)
Destination: DEVCLNT100 (handle: 4, 73508497, {54C4E81F-7BD3-051D-E100-0000AC180AF2})
**** Trace file opened at 20150126 123459 CET SAP-REL 640,0,155 RFC-VER 3 865711
======> Client XXX is not available. Please choose an existing client
ABAP Programm: SAPLERFC (Transaction: BD87)
Called function module: ARFC_DEST_SHIP
User: ALEUSER (Client: XXX)
Destination: DEVCLNT100 (handle: 1, 74404664, {54C4E9BD-7BD3-051D-E100-0000AC180AF2})
**** Trace file opened at 20150126 123619 CET SAP-REL 640,0,155 RFC-VER 3 865711
======> Client XXX is not available. Please choose an existing client
ABAP Programm: SAPLARFC (Transaction: BD87)
Called function module: ARFC_DEST_CONFIRM
User: ALEUSER (Client: XXX)
Destination: DEVCLNT100 (handle: 2, , {54C4E9BE-7BD3-051D-E100-0000AC180AF2})
Of course system is defined in SCC4, logical systems are correctly assigned.
Before client copy ALE worked ok.
Any ideas how to correct this error?
Best regards,
Sasha

Hi Raymond,
All is well in SM59.
Since we copied data only during client copy this conversion should have been already made during that process as is written in BDLSS. We did copy client from PRD to QAS before and we did not need to run BDLSS for ALE to run ok.
Could BDLSS resolve this?
Regards,
Sasha

Problem in BD64 for HRMD_ABA message type

Hi,
Iam using HRMD_ABA Message Type in distribution model(BD64).
My requirement is that i want to add status of the employment in the Filter Group.
i.e.: in BD64 transaction>under HRMD_ABA>data filter active>filter group>infotype-->(will be 0000)
-->Object type(Will be 'P' for person)
Now where i will put status value as '3'.....?
Thanks in advance..
Regards.

HI,
it seems you have to add new filter objects.
Check tcode BD95 and BD59 to add new filter objects.

Model view (t-code- bd64) configuration issue

1) Is it possible with out distributing customer distribution model in outbound side ,can we receive idoc data in inbound side?
2) after distribution of model view in outbound side is it possibel to create filter techniqe in inbound side?
Thanks
Bhaskar Reddy

Hi,
1) Is it possible with out distributing customer distribution model in outbound side ,can we receive idoc data in inbound side?
- Yes, if is not MASTER data, probably you do not need to configure BD64 for outbound IDoc.
2) after distribution of model view in outbound side is it possibel to create filter techniqe in inbound side?
- You can filter in the Distribution Model easily. So you should use it for filtering data. Otherwise you need to filter it programmatically in some customer-exit.

IDOC filter problem in BD64

Hi,
I created a filter in BD64 for message type ZDEBMAS with account group(ZSB) of customer as the filter. If you give other than ZSB customer account group, it is suppose to skip the IDOC.
But it is throwing error "internal error: Program read table idoc_structure, command data_select_for_block, argument Z1ADRC".
Here Z1ADRC is the custom segment in ZDEBMAS.
What can be the problem. Please help me out of this .

Hi Janardhan,
I had created the model view for ZDEBMAS and generated partner profile. As i am sending to non SAP system (Siebel) no need to distribute the model view.
IDOC getting generated for ZSB account group customers, problem is with the other account group customers.
The Error i got after adding the filter in BD64 for account group.
Any other clue.

Software Distribution - Problem with 1921 Routers

Hello everybody,
we are having some weird troubles in our Cisco LMS 4.2
A Software Distribution works fine for all kinds of our Routers, except the 1921 models. We are using SCP and SSH for the Image distribution and the exactly same configuration on a 1841 and a 1921 works on the 1841 Router but on the 1921 not.
I didn't found any Bugs related to this, maybe it's a problem with the lms settings?
Done so far:
- Deleted the device in LMS, added it via discovery and manually, no change here
- Tried with different IOS versions, no change here, no one will work
- Set the credentials after adding the device again, to make sure they are valid
When creating a new distribution job, we get this error at Step 3 of 5 only at the 1921 Router, so I guess this might be the problem:
Warning
- SWIM1056: The method to update the software on the selected storage device is unknown.
Select a different Flash partition, if available.
I attached a SWIM_debug logfile from a failed job. (changed all the DNS names do XXXDNSNAMEXXX).
Thanks for your help

More than USB it could be SCP. There is a know bug for SCP on 19xx router :
CSCuc98074 LMS 4.2.2 Software Image Distribution fails with SCP on 1921 routers
Just try to change SCP to other protocol and see it that works. Make sure you have all device packages updated for LMS.
-Thanks
Vinod
**Rating Encourages contributors, and its really free. **

Distribution filter in BD64 with qualifier

Hello,
I have to create a filter in BD64 for message type ORDERS for Company code. I can do configuration in BD95 and BD59 to make Company code appear in filter list in distribution model.
Now Issue:
Comapny code(ORGID) appears in standard segment E1EDK14 with qualifier(QUALF) 011.
How can I define filter for E1EDK14-ORGID for qualifier 011 only.
E1EDK14 can appear many times with different qualifiers.
Please don't suggest for a separate Z segment
Thanks in advance,
Kumar

Hi ,
Unfortunately we don't have the IF logic here like Kernel BADI.
Please find the Enhancement Spot or Point and Last thing is Implicit Enhancement.
Consider the : Message type ,BASIS type and Company Code. ( It will be great if you implement the Kernel BADI inside a Implicit Enhancement as this may be enhance to other company code or Message type)
BR,
Bharani

Can't extend network: AE models the problem?

checking out some other messages I searched out here, I suspect I may have the problem figured out, more or less, but need to figure out how to be sure:
I have 5 airport expresses, bought at different times, that make up a home network designed to play music via a pair of speakers attached to each AE, and one main is attached to a cable modem.
This works ok, though I get a lot of dropout as complained about by many others here, not consistent enough to blame my other electronics in the house, although who knows what the downstairs neighbor might have that is interfering.
Hoping to improve the robustness of the system, I tried to set up the AE to extend the network rather than just join it, but got a lot of error messages when airport utility was trying to 'configure main network' to accept an extension via this airport. I did type in MAC addresses for each additional devices into the main (modem connected) AE settings, under 'allow clients', and it seemed to reset with that data accepted/intact. I just couldn't 'extend' via the clients as I added them.
Which AE models are configurable to extend a WDS network? And does it matter which of them is the 'main' and which are the 'relay' devices? And can I interrogate the AE to tell which model they are or do I have to squeeze into their nooks and try to read the very fine print on them?
I really only need one of them to do the 'relay' thing to the printers, and if one of them is compatible with that function and the others were not, it would save a lot of time to know which one it is, or that I have to replace just that one.

Which AE models are configurable to extend a WDS network?
Both the 802.11g (Model# A1084 / Part# M9470LL/A) & 802.11n (Model# A1264 / Part# MB3211LL/A ) AirPort Express Base Stations can be configured for a Wireless Distribution System (WDS) to extend their network wirelessly. However, depending on which model you have, the configuration steps to do so are different.
There are basically two "flavors" of WDS: static & dynamic. The 802.11g models can only support static, and the 802.11n models can do either. In the case where you would use mixed versions, only the static option is available.
A static WDS allows for a main, relay, and remote base stations in the configuration. It is better suited when you want to cover a long linear distance ... like a rectangular-shaped building. On the other hand, a dynamic WDS only allows for a main and (multiple) remote base stations. This is better suited for those situations where the main would be in the center and you wanted to extend the network outwards to other rooms. Think of a star pattern.
And does it matter which of them is the 'main' and which are the 'relay' devices?
The "main" should be the one connected to the Internet.
And can I interrogate the AE to tell which model they are or do I have to squeeze into their nooks and try to read the very fine print on them?
The simplest way would be to use the AirPort Utility and check which firmware version a particular base station is using. The 802.11g models use v6.x; the 802.11n models use v7.x.

Automatic Mailbox Distribution problem after Creating New AD Site

We redesigned our Active Directory Sites a little while ago. We moved the subnets and servers from the old sites to the new sites. We haven't removed the old sites yet, but that will happen soon. We haven't noticed any issues with the new
sites except for one weird issue and that is that Automatic Mailbox Distribution no longer works, in fact if you don't specify a database with the enable-mailbox (or new-mailbox) commands it will fail with an error that load balancing failed to find a valid
mailbox.
The problem, from the output of an enable-mailbox, command appears to be a site problem (from the fact that the automatic mailbox distribution discards sites that are not in the same site as the user). The verbose output has the command checking the
old site even though the server is in the new site. I've already checked the databases and none of them have the IsExcludedFromProvisioning or IsSuspendedFromProvisioning properties set to TRUE
My question is how do I make the databases show up as in the new site rather than the old site?
Any and all help with this issue is appreciated.
This is the output from the command:
VERBOSE: [16:36:50.864 GMT] Enable-Mailbox : Initializing Active Directory server settings for the remote Windows
PowerShell session.
VERBOSE: [16:36:50.864 GMT] Enable-Mailbox : Active Directory session settings for 'Enable-Mailbox' are: View Entire
Forest: 'False', Default Scope: 'domain.local', Configuration Domain Controller: 'DC01.domain.local', Preferred Global
Catalog: 'VMDC01.domain.local', Preferred Domain Controllers: '{ VMDC01.domain.local }'
VERBOSE: [16:36:50.864 GMT] Enable-Mailbox : Runspace context: Executing user: domain.local/All Users/AD/Admin1,
Executing user organization: , Current organization: , RBAC-enabled: Enabled.
VERBOSE: [16:36:50.864 GMT] Enable-Mailbox : Beginning processing &
VERBOSE: [16:36:50.880 GMT] Enable-Mailbox : Instantiating handler with index 0 for cmdlet extension agent "Query Base
DN Agent".
VERBOSE: [16:36:50.880 GMT] Enable-Mailbox : Instantiating handler with index 1 for cmdlet extension agent "Rus Agent".
VERBOSE: [16:36:50.880 GMT] Enable-Mailbox : Instantiating handler with index 2 for cmdlet extension agent "Mailbox
Resources Management Agent".
VERBOSE: [16:36:50.880 GMT] Enable-Mailbox : Instantiating handler with index 3 for cmdlet extension agent "Mailbox
Creation Time Agent".
VERBOSE: [16:36:50.880 GMT] Enable-Mailbox : Instantiating handler with index 4 for cmdlet extension agent
"Provisioning Policy Agent".
VERBOSE: [16:36:50.880 GMT] Enable-Mailbox : Instantiating handler with index 5 for cmdlet extension agent "Admin Audit
Log Agent".
VERBOSE: [16:36:50.927 GMT] Enable-Mailbox : Current ScopeSet is: { Recipient Read Scope: {{, }}, Recipient Write
Scopes: {{, }}, Configuration Read Scope: {{, }}, Configuration Write Scope(s): {{, }, }, Exclusive Recipient Scope(s):
{}, Exclusive Configuration Scope(s): {} }
VERBOSE: [16:36:50.927 GMT] Enable-Mailbox : Searching objects "domain.local/All Users/SM/GP/User1" of type
"ADUser" under the root "$null".
VERBOSE: [16:36:50.942 GMT] Enable-Mailbox : Previous operation run on domain controller 'VMDC01.domain.local'.
VERBOSE: [16:36:50.974 GMT] Enable-Mailbox : Load Balance : Database container located at 'CN=Databases,CN=Exchange
Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=DOMAIN,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=local'.
VERBOSE: [16:36:50.974 GMT] Enable-Mailbox : Searching objects of type "MailboxDatabase" with filter
"(&((IsExcludedFromProvisioning Equal False)(IsSuspendedFromProvisioning Equal False)(Recovery Equal False)))", scope
"OneLevel" under the root "Databases".
VERBOSE: [16:36:51.005 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.021 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.021 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.021 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.021 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.021 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.036 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.036 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.036 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.036 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.036 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.036 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.052 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.052 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.052 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.052 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.067 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.067 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.067 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.067 GMT] Enable-Mailbox : Comparing local site 'OLD-SITENAME' with database site 'OLD-SITENAME'.
VERBOSE: [16:36:51.067 GMT] Enable-Mailbox : Load Balance : The search for databases returned an empty result. This
could happen if all databases are excluded from the Load Balance process.
VERBOSE: [16:36:51.067 GMT] Enable-Mailbox : Load Balance : There is no available database. Refer to previous verbose
messages for more information.
VERBOSE: [16:36:51.067 GMT] Enable-Mailbox : Admin Audit Log: Entered Handler:OnComplete.
Load balancing failed to find a valid mailbox database.
+ CategoryInfo : NotSpecified: (0:Int32) [Enable-Mailbox], RecipientTaskException
+ FullyQualifiedErrorId : 4AE0EA04,Microsoft.Exchange.Management.RecipientTasks.EnableMailbox
VERBOSE: [16:36:51.083 GMT] Enable-Mailbox : Ending processing &

Hi,
From your description, I would like to clarify the following thing:
By default, all online and healthy mailbox databases on Exchange 2010 servers in the local Active Directory site can be chosen by automatic mailbox distribution to store a new or moved mailbox. Mailbox databases in other AD site can't be chosen by automatic
mailbox distribution to store a new or moved mailbox.
What's more, I recommend you use the following cmdlet to enable mailbox and check the result.
Enable-Mailbox -Identity xxx -Database xxx
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

Logical model - 2 problems (proposal to improve)

hi,
1st problem:
New entity - Add attribute - Primary UID - Apply (Unique identifier is created)
After Primary UID unchecking the Unique identifier is still there, so after OK or Apply, an Error message (Incoplete Unique Identifier) is displayed.
Now it is necessary to modify/delete Unique identifier manually - could it be this operation automatized?
2nd problem
after duplication of Entity with Unique identifier (Copy - Paste) the new Entity is renamed right, but name of UI in new Entity is unchanged.
this cause problem after Engineer - DDL with duplicate constraint name
thank u,
mat

Quote
I recently bought 2 GB of 333Mz PC2700A DDR RAM
Please post the brand name and model/serial number of these modules. Look at the modules themselves to find that information (sticker/chip markings).
Quote
Name : Version 1.00
If you have an MS-6580 Version 2.x board you BIOS Version should not be 1.00. Please check you current BIOS Version on the POST Screen und post the full BIOS ID String:
Also, do verify you mainboard model, look at the board itself. Don't trust any software tools:
How to identify your BIOS and m/b version
Quote
OEM 230V cannot find out what Wattage it is.
For PSU details, look at the sticker on the PSU. Look for:
- brand name
- model name/model number
- amperage limits (A) on main voltage rails (12V, 5V and 3.3V)

Model Distribution Problem in BD64

Similar Messages

Maybe you are looking for