Issue for IDOC while converting XI party for acks
Hi all,
I've setup a scneario IDOC to external company ( RNIF 1.1 adapter ) over XI. During my tests I get the error when the system sends back an acknowledgement 'Unable to convert sender XI party http://sap.com/xi/XI/XIParty/Party_one' to an IDoc partner.
Why does the system tries to convert the 'Party_one' party to an IDOC partner ? What wold he try to update in sending system ?
( My outbound purchase order idoc has a 'LS' partner as sending IDOC partner and a 'LI/LF' as receiving idoc partner
Any idea on where to add this mapping ?
( I have not setup any ALE audit acks, nor any specific Idoc channel for acks. Should I ? )
Any ideas ?
rgds
Dirk
Hi Dirk,
You can block the ack using report IDX_NOALE
Regards
Vijaya
Similar Messages
-
MSCOBJCL.sql runs for long while applying patch 6678700 for 12.1.1 upgrade
DB:11.2.0.3.0
OS: IBM AIX Power system 64 bits 6.1
Hi All,
MSCOBJCL.sql runs for long while applying patch 6678700 for 12.1.1 upgrade. We are upgrading from 11.5.10.2.0 to 12.1.1
Could anyone please share why the script takes so much of time to run?
Thanks for your time
Regards,a1_winAs per Mscobjcl.Sql Is Running Long While Applying Patch.8671960 (Doc ID 1295881.1)
The patch is already applied in the instance
BUG_NUMBER CREATION_DATE
8671960 19-SEP-10
Thanks,
a1_win -
BAPI for Assigning multiple ship to party for customer
Hi experts,
I need a bapi to assign different ship to party for a customer.
I have tried SD_CUSTOMER_MAINTAIN_ALL but not working properly.
Kindly suggest the solution.
Regards,
Nitin.Hi,
For the maintenance of customers, there is NO BAPI and NO direct function module.
There are some functions modules like the one above where the name is looking nice. But these should not be used.
Below ECC 2005 (6.00), the only solution was batch input and DEBMAS idocs. See [note 384462|https://service.sap.com/sap/support/notes/384462]
Starting with ECC 2005 (6.00) and above: a synchronisation tool has been introduce. See class CMD_EI_API and VMD_EI_API
Hope this helps
BR
Alain -
Not asking for TR while re-creating TMG for DB Table?
Hello Folks,
I have added the field in the DB table in DEV server but it wont reflect on Quality server. I cheked it on DEV, it is showing there. There is no issue with the SM30 also. But still it wont reflect on quality. So I deleted the existing TMG & created the new one. but while creating the new one, it didn't asked me to for new TR. My problem is that how I move this newly created field onto quality server?
Thanks in advance.Thanks a lot Vadamalai Adhimoolam & chandra madapati ...I have done as suggested by you. Now, awaiting for the functional guy's reply...
-
Is that possible?
mende1
wrote: For most apps, it's possible, but there are other which will give you troubles.
In my experience, with most of the apps that I use on a regular basis, most must be installed on the boot drive. You can't just 'move', for example, Adobe CC applications, Office apps (as you note), etc.
If I were the OP, I would install all apps on the SSD - they actually take up very little room - and insatll only user files, etc., on an external drive.
Just my 2¢...
Clinton -
Hi am interested to learn about idocs can you provide me some useful links
Hi saranya srithar ,
IDoc is an Intermediate document that holds application data.
A container used to exchange data
It is independent of the complex SAP structure to store data.
It serves as the vehicle for data transfer.
IDoc Type defines the structure and format in which the data is exchanged.
It is similar to a structure in SAP
IDoc data is an instance of IDoc Type
IDoc acts as a standard SAP interface to exchange business data through ALE.
From an SAP system, an IDoc can be sent to and received from
An SAP R/3 system
An SAP R/2 system
An EDI subsystem
Any third-party application software
Segments . Idoc data is arranged in Rows, The rows make up segments of an idoc. Each segment consists of fields/segments. Fields can contain data.
These r all the t/codes which we will come across in IDocs:
TCODE TTEXT
BD10 Send Material
BD100 IDoc display object channel view
BD101 Consistency check
BD102 Outbound registry
BD103 Inbound registry
BD104 maintain tbd53
BD105 Maintain Supported Business Objects
BD11 Get Material
BD12 Send customer
BD13 Get customer
BD14 Send vendor
BD15 Open vendor
BD16 Send Cost Center
BD17 Get Cost Center
BD18 Send General Ledger Account
BD19 Get General Ledger Account
BD20 IDoc passed to application
BD21 Select change pointer
BD22 Delete change pointers
BD23 Delete serialization data
BD24 Send Cost Elements
BD25 Send Activity Type
BD26 Get Activity Type
BD27 Send cost center activity prices
BD28 Send obj/cost element control data
BD30 Distribute material object list
BD31 Distribute document object list
BD32 Distribute plant allocations(matBOM)
BD33 Distribute material variants (ALE)
BD34 Distribute order BOM
BD35 Send Business Process Groups
BD36 Send Business Processes
BD37 Send Business Process Price
BD40 Read change pointer for group
BD41 Dispatch IDocs for group
BD42 Check IDocs for group
BD43 Post IDocs for group
BD44 Assign Message Types to Serlz. Group
BD47 Dependencies between methods
BD48 Dependency method - message
BD50 Activate Change Ptrs for Mess. Type
BD51 Maintain function modules (inbound)
BD52 Activ.change pointer per chng.doc.it
BD53 Reduction of Message Types
BD54 Maintaining Logical Systems
BD55 Maintain IDoc Conversion
BD55OLD Maintain IDoc Conversion
BD56 Maintain IDoc Segment Filters
BD57 Maintain link and serialization ty.
BD58 Convert organizational units
BD59 Allocation object type -> IDoc type
BD60 Additional data for message type
BD61 Activate Change Pointers - Generally
BD62 Define Segment Conversion Rule
BD62OLD Define Segment Conversion Rule
BD63 Transport ALE Tables of Message Type
BD64 Maintenance of Distribution Model
BD65 Maintain IDoc type required fields
BD66 IDoc type field -> change doc.field
BD67 Maintain methods (inbound)
BD68 Maintain Lists
BD68OLD Maintain Lists
BD69 Assignment of Message Type to IDoc
BD70 Synchronize Number Ranges
BD71 Define FM for dependent bus. object
BD72 Activate Events
BD73 Reposting of IDocs (ALE)
BD75 Convert IDoc Status
BD77 Distribution of control data
BD78 Monitoring control data distribution
BD79 Maintain IDoc Conversion Rules
BD79OLD Maintain IDoc Conversion Rules
BD81 Filter objects parameter filtering
BD82 Generate Partner Profiles
BD83 Send IDocs after an ALE error
BD84 Post IDocs after ALE error
BD85 Consistency check for transfer
BD86 Consistency check for sales
BD87 Status Monitor for ALE Messages
BD89 Control data model. - initial screen
BD91 Send Characteristic
BD92 Send Class
BD93 Send Classification
BD95 Specify ALE object types
BD96 filter objects of receiver determin.
BD97 Assign RFC dest. to Logical Systems
BD98 Consistency Check Workflow Connectn.
BD99 Message type dependencies
WE02 Display IDoc
WE05 IDoc Lists
WE06 Active IDoc monitoring
WE07 IDoc statistics
WE08 Status File Interface
WE09 Search for IDocs by Content
WE10 Search for IDoc in Archive
WE11 Delete IDocs
WE12 Test Modified Inbound File
WE14 Test Outbound Processing
WE15 Test Outbound Processing from MC
WE16 Test Inbound File
WE17 Test Status File
WE18 Generate Status File
WE19 Test tool
WE20 Partner Profiles
WE21 Port definition
WE23 Verification of IDoc processing
WE24 DefaultValuesForOutboundParameters
WE27 DefaultValues for Inbound Parameters
WE30 IDoc Type Development
WE31 Development IDoc Segment
WE32 Development IDoc View
WE34 Object for Display of XML IDocs
WE40 IDoc Administration
WE41 Process codes, outbound
WE42 Process codes, inbound
WE43 Funct.module: Status record display
WE44 Partner Types and Checks
WE45 Forward (inbound) (V3, EDILOGADR)
WE46 Error and Status Processing
WE47 Status Maintenance
WE50 System process codes: Texts
WE51 System process codes: Change texts
WE54 FMs for changing file names
WE55 Function Module for Path Names
WE56 IDoc Administration
WE57 Assignment Messages for Appl. Objs
WE58 Status process codes: Texts
WE59 Change status process codes
WE60 Documentation for IDoc types
WE61 Documentation for IDoc record types
WE62 Documentation for segments
WE63 Documentation
WE64 Documentation message types
WE70 Conversion: Basic types
WE71 Conversion: Extensions
WE72 Conversion: IDoc types
WE73 Conversion: Logical messages
WE81 Logical message types
WE82 Assign Messages for IDoc Type
WE84 Assignment of IDoc and appl. fields
WE85 Create Rule Names
WEBU Printing Labels via Assortment List
WEDI EDI Basis
WEINBQUEUE IDoc Inbound Queue
WEKF Purchase order SAP Retail
WEL0 Forward (inbound) (EDILOGADR)
WEL1 EDI: Interface Invoice for EDILOGADR
WELI Maintain Status Groups
cheers!
gyanaraj -
Dear friends ,
can any one give me important Tcodes for IDOC & workflow
ReddyTcode list for ALE IDOC:
ALE / EDI/ IDOCS TRANSACTION CODES
Transaction Code Description
WE02 List Of All Idocs Created. (Default, Additional, EDI)
WE05 List Of Idocs Created. (Standard, Additional)
WE06 Active Monitoring For Idoc Processing.
WE07 Idoc Statistics.
WE08 Display View u201CFile Statusu201D:Overview-Path Name.
WE09 Idoc Search For Business Contents (Database).
WE10 Idoc Search For Business Contents (Archive).
WE12 Modification Of Outbound File, Triggering Inbound Processing.
WE14 Process All Selected Idocs.
WE15 Selection Program For Issuing Output.
WE16 Trigger Inbound Processing.
WE17 Trigger Status Processing.
WE18 Generate Test Status File For Outbound Idocs.
WE19 Test Tool For Idoc Processing
WE20 Partner Profile.
WE21 Ports In Idoc Processing.
WE23 Display Test Catalog Test Idoc Interface.
WE24 Maintain Table View. Direction-1.(Outbound)
WE27 Maintain Table View. Direction-2.(Inbound)
WE30 Develop Idoc Type.
WE31 Develop Idoc Segments.
WE32 View Development.
WE33 Maintain Table Views.
WE34 Change View u201CTable Of Style Ids With The Objects To Be Loadedu201D
WE40 Display System Process Code.
WE41 Display View: Logical Msg Overview. For Outbund.
WE42 Display View: Logical Msg Overview. For Inbound.
WE43 Display Status Records.
WE44 Display Partner Types
WE45 Maintenance Interface: Forwarding Inbound/EDILOGADR For Application
WE46 Global Parameter For Idoc Interface.
WE47 Status Maintenance.
WE50 Display Text For Process Code System.
WE54 Idoc Function Module For File Name
WE56 Display Status Process Code
WE57 Idoc Assignment Of FM To Log. Message And Idoc Type.
WE58 Text For Process Code Status.
WE60 Documentation For Idoc Type.
WE61 Documentation For Idoc Record Type.
WE62 Documentation For Idoc Segment Type.
WE63 Documentation For Idoc Record Types And Idoc Types (Parser).
WE64 Process Code In Idoc Inbound And Outbound.
WE70 Conversion Table For Basic Types.
WE71 Conversion Table For Extensions.
WE72 Conversion Table For Field DOCTYP.
WE73 Conversion Table For Logical Message Type.
WE81 EDI:Logical Message Type.
WE82 Message Types And Assignment To Idoc Types.
WE84 Assignment Table Between Idoc And Application Field.
ALE / EDI/ IDOCS TRANSACTION CODES
Transaction Code Description
BD10 Send Material (Matmas)
BD11 Get Material.
BD12 Send Customer.
BD13 Get Customers
BD14 Send Vendor.
BD15 Get Vendor.
BD16 Send Cost Center. (Cosmas)
BD17 Request Cost Center.
BD18 Send G/L Accounts.
BD19 Get Master Data G/L Accounts.
BD20 Inbound Processing Of Idocs Ready For Transfer.
BD21 Creating Idoc Types For Change Pointers.
BD22 Delete Change Pointers.
BD23 Serialization Using Time Stamp: Deletion Of Old Time Stamp.
BD24 Send Cost Elements.
BD25 Send Activity Type (COAMAS)
BD26 Request Activity Type
BD27 Cost Center/Activity Types: Transmit Plan Quantities And Acty Prices.
BD28 Cost Center/ Cost Elements: Send Control Records.
BD30 Material Bom Distribution. (Bommat).
BD31 Document Structure Distribution. (Bomdoc)
BD32 Plant Allocation To Material Boms Distribution.
BD33 Distribution Of Material Variants. (STTMAT)
BD34 Distribution Of Boms (BOMORD)
BD35 ALE: Send Business Process Group.
BD36 ALE: Send Business Process.
BD37 ALE: Send Business Process Price.
BD40 Generate Idocs For Serialization Group From Change Pointers.
BD41 Dispatch Of Idocs Of Serialization Group.
BD42 Check Dispatch Status Of Idocs Of Serialization Group.
BD43 Processing Inbound Idocs Of Serialization Group.
BD44 Change View u201CSerialization Groupu201D.
BD47 Dependence Between Methods.
BD48 Dependence Between Methods And Message Type.
BD50 Activate Change Pointers For Message Type.
BD51 Characteristics Of Inbound Function Module.
BD52 Determine Work Area.
BD53 Reduce Message Type.
BD54 Change View: Logical Systems
BD55 Idoc Conversion.
BD56 Maintain Idoc Segment Filters.
BD57 Link Type And Serialization Type Of Message Type.
BD58 Convert Organizational Unit.
BD59 Allocation Of Object Type.
BD60 Additional Data For Message Type.
BD61 Activate Change Pointers Generally.
BD62 Display Conversion Rule.
BD63 Transport Of Ale Tables For A Message Type.
BD64 Display Distribution Model.
BD65 Maintain Idoc Type Required Fields.
BD66 Change Idoc Fields.
BD67 Function Module For ALE/EDI Overview.
BD68 Maintain List.
BD69 Assignment Of Idoc Type To Message Type.
BD70 Cross-System Comparison Of Number Range Objects.
BD71 Attributes For Receiver Determination.
BD72 Active Events For ALE/EDI
BD73 Start Error Handling For Non-Posted Idocs.
BD75 Status Conversion With Trfc Execution.
BD77 Generate Transport Requests For Distributing ALE Customizing Data.
BD78 Monitoring Ale Customizing Data Transport
BD79 ALE IDOC Segments - Conversion Rule
BD81 Filter Objects For BAPI Parameter Filtering
BD82 Generating Partner Profile
BD83 Re-Processing Incorrect Outbound Odocs.
BD84 Re-Processing Of Idocs After ALE Input Error.
BD85 Consistency Check: Reassignment Between Two System.
BD86 ALE Consistency Check: Create Purchase Order From Sales Order.
BD87 Select Idocs
BD89 Customizing Data Modeling For Distribution Model.
BD91 Distribute All Characteristics Via ALE.
BD92 Distribute Class Via ALE: Send Direct.
BD93 Distribution Of Classification Data Via ALE.
BD95 Ale Object View
BD96 Filter Object For Receiver Determination Of Methods.
BD97 Assign RFC Destination For Synchronous Method Calls.
BD98 Consistency Check With Workflow Link
BD99 Dependencies Between Message Types.
BD100 Display Serialized Idocs. (Serialization Using Object Types)
BD101 Serialization Using Object Types: Consistency Check.
BD102 Ale: Outbound Channel Registry. -
Need all transaction codes for idocs
need all transaction codes for idocs
Hi,
ALE IDOC
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
I know how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
BAPI tcode --- BAPI.
Also:
IDOC:
IDOC ADMINISTRATION
WE09 / WE02 IDoc lists according to content. View IDocs via specific IDoc number or business application detail contained within the contents of a segment.
WE05 View IDocs
WE60 IDoc type documentation tool
WE20 Partner profile configuration. Add partner detail together with inbound and outbound relationships. We also incorporate message control on the outbound IDocs. Utilize the organizational units to trap functional errors for further processing.
BD87 Reprocess IDocs in error or waiting for action. (Both inbound and outbound in 4.6. Use BD88 in prior versions)
1.4 IDOC DEVELOPMENT
BD55 Conversion rule user exit. Link conversion rule user exit to the different system \ partner combinations.
WE19 EDI test tool. Use to test inbound Function module changes.
WE31 Segment create
WE30 Create IDoc extension type
WE82 Link Release detail to Extension IDoc Type
WE57 Assign function module to logical message and IDoc type
BAPI: BAPI, SWO1.
Transaction codes Related for IDOC Configurations
WEDI: Area Menu for IDOCs
WE02: Display IDoc
WE19: ALE Test tool
WE30: Development of IDOC Type
WE31: Development of IDOC Segment
WE41: Process Codes, Outbound
WE42: Process Codes, Inbound
WE47: Status Maintenance
WE81: Logical Message Types
WE57: Assignment Messages for Appl. Objs
SM59: RFC Destinations (Display/Maintain)
SALE: Display ALE Customizing
BD54: Maintaining Logical Systems
BD67: Maintain methods (inbound)
BD64: Maintenance of Distribution Model
BD87: Status Monitor for ALE Messages
Reward points if found helpful...
Cheers,
Chandra Sekhar. -
Hi Gurus,
i have a problem in Idoc, while creating output type for a Billing document that time one segment repeating lots of time with same data..how to avoid this?
MohanaMohana
Are you sure about the segment name E1EDK01 ?? Becoz.. Only one Segment of type E1EDK01 is allowed in one IDOC...
See below for details:
Segm.type E1EDK01
Minimum number 1
Maximum number 1
Parent segment
Hier.level 1
Thanks
Amol Lohade -
G5 dual 2ghz. Been unplugged for a while. Powers up but no video or power to usb keyboard. Boots up fine in safe mode, restart into normal mode ok. After shutdown, back to same issue. What's happening?
I keep seeing people ask and the advice to replace if it has been unplugged, but really have nothing to confirm that from my experiences.
My experience is that a weak or dead battery can cause much more than date and time issues.
I have seen it time and time again.
Deal with used machines and you will quickly learn....
I'll give no "recipe" or set list of symptoms, but the range of irregularities that can occur make it a quick and easy first line of troubleshooting, especially when the machine has been off the mains for a few months.
Why fight mysterious maladies and troubleshoot with the knowledge that the PRAM battery is beyond it's useful life.
Maybe they recharge?
Not likely. They are chemically nasty, disposable, one way discharge batteries.
They aren't Lithium-ion batteries -
Open qty errin Selection list For Ref Doc. screen while converting to order
Hi SAP Gurus,
For one of my materials, the open quantity is not updating in the Selection list For Ref Doc. screen while converting to sales order.
Can you please help me?
Thanks,
KetanHi Senthilkumar,
I really appreciate for your kind Hint of SEL ID.
I created and assigned new 'Sel Priority' to the SEL ID same as for Routing.
Now while converting Planned order to Production order system is asking for Reference operation set as there is no such need of Routing as I already mentioned in previous post.
Regards, -
So yes like mentioned above...i am a new mac user...have only had it about four days and have had a windows based system always before this. The issue I am having is that I will be in safari and it will work perfect for a while and then i will open a new tab and attempt another website and it will either be extremely slow or will give the error that it cannot connect to the server, however, when i run diagnostics my internet is fine. The only solution i have found is to reboot and geeksquad has been unable to replicate the problem while connected to my computer to try to do so. Does anyone have any suggestions or anyone else with this problem? If you have a "fix" please try layman's terms because again I have no idea about macs haha. Thanks,
So yes like mentioned above...i am a new mac user...have only had it about four days and have had a windows based system always before this. The issue I am having is that I will be in safari and it will work perfect for a while and then i will open a new tab and attempt another website and it will either be extremely slow or will give the error that it cannot connect to the server, however, when i run diagnostics my internet is fine. The only solution i have found is to reboot and geeksquad has been unable to replicate the problem while connected to my computer to try to do so. Does anyone have any suggestions or anyone else with this problem? If you have a "fix" please try layman's terms because again I have no idea about macs haha. Thanks,
-
Is anyone else having issues with "skipping" while the songs are playing?! It is very aggravating to us... and we've had it going on for several months now. Any ideas at all how to fix it?
So, don't use youtube.
http://www.the-top-tens.com/lists/best-alternatives-youtube.asp
http://www.youtubealternative.com/ -
Error while converting planned order to production order for config materia
Hi experts,
While converting a planned order to production order for a configurable material.I am getting the following error meassage. Message No.CO684,
"You cannot make an assignment to make-to-order stock"
( DiagnosisThe component cannot be allocated to an individual stock because make-to-order production and engineer-to-order production cannot be executed with this order.
A possible cause is that you are trying to create an order with reference to a sales-order/project, where an account assignment to a sales order/project is not allowed in the settlement profile that is assigned to the chosen order type. This is inconsistant.
System ResponseThe following responses are possible:
Order processing is cancelled.
The system resets the special stock indicator back to the original value.
Procedure
Choose another order type).
I have checked some of the threads related to this error. But no where there is any solution.Please tell me if there is any settings to make so as to work on this scenario.
Thanks,
ShamHi,
This will be a MTO scenario. Please check your requirement type,Requirement class and strategy type config along with your Item category and schedule line category from SD.
Also check your Production order type config and settlement profiles.
I mean to say that you need new production order type to be configured for specific above mentioned combination.
Are you working on a production system..?? is it the first time you are creating the order for this config material..??
Regards, -
Although I have been using Google Maps App in India for a while now (without any issues) but I still want to know if there are any plans for launching Turn by Turn Navigation under the OOTB Map App for iOS?
It has been quite a while since Apple came up with Map App of their own and should be releasing improved maps with more capabilities in India.
Cheers!
AbhishekNo one here can answer your question, as there is no one from Apple here, & no one here represents Apple or speaks for Apple.
Maybe you are looking for
-
Cannot upgrade my Nokia 500 to Belle
Hi There, I'm trying to update my Nokia 500 to Belle but I get an authentication error. I'm usign Nokia Suite v 3.7.22 in Windows 7 x64. Please any idea ? Thanks in advance.
-
Windows don't recognizes my DVD drive
If I insert a disc nothing happens. When I open Device Manager and look at the Root, the DVD/CD driver is installed. In a subfolder (marked with a yellow triangle) it said: Device status: Windows cannot load the device driver for this hardware. The d
-
Custom text tones in iOS 5 not working
Hey, I recently updated to iOS 5 as did everyone else. but when I get a tweet it doesn't play the tweet tone, all I get is tri-tone. The text tone works fine enough, but the twitter ones dont . Is that normal? Also, I've noticed the battery life on m
-
After click restore button the restore started but it only go up to 75% then it got drop. This is for iPad2. Please advise. Thanks.
-
Can't change blank Composer in just-bought iTunes album
Subject says it all really. I just bought a classical album ("English Landscapes") from the iTunes Store. After downloading completed I saw that Composer was blank in all 8 tracks. When I try to fix this in the Library, by clicking twice in the Compo